 But I welcome a banner bunch. Harry, how's it going this morning? So there's standard agenda. We're going to introduce everybody on the team. Put some names to faces, faces to names. Then we're going to talk about job submission. Everyone just cheers, right? Yay! Actually, I like talking about job submission, because it's an area I think you can always use a little bit of clarity. It's always a little pleasant. It's a little space. It's always good to have a little bit more clarity on it. And then we'll have our usual open form. After we're done training on job submission, you can ask any question you want. You can dive deeper into the areas. So without further ado, we are in your banner bunch. We've got Kimmy, Mark, Tyler and actually on vacation today. Theresa, Laurie, Carl, Lee is back in the office. Catherine, myself on the team, and Michael was actually at a conference today. So, what is job submission? What is a job? It's a term that's kind of thrown around a little bit. But I'd like to provide a little bit of clarity, as I usually like to do, and just make sure we've all got the same definitions we need to create. So a job is just a program. It's an algorithm. It's a set of instructions we can give the database and it'll just do something. That's pretty much it. It's just a set of instructions. But it comes in two different players. Jobs can either change data in the system or they don't change data. So a report is one of those ones that doesn't change data. A report just looks at the database, grabs up a whole bunch of stuff, and then reports it back to you and hopefully a readable format. It might condense some things. It might make a summary of information that's out there in the database, but it's just showing you what exists out there in the database. Now, a job that does make changes, we call a process. A process will go out and actually based on whatever criteria we give it or the business process we're doing, will actually make changes to the information in the system. That's really the key difference because we don't report the process. Does it change data? Or does it not? Job report process. We can use these terms all interchangeably so it can get a little confusing, but that's really all it comes down to. They're all jobs. They either change data or they don't. And you can usually tell if a job is a process or a report just by looking at the name of it and not kind of show that as we go. The third character in the name would either be an R or P, and that's usually correct. I like the word usually. I have to use the word usually because can we correct you if I say it's all the time? No, no, no, not a correction. Just don't be surprised when you report it actually. Sometimes the naming scheme is not perfect. The other thing you kind of think about here at Lynn Benton, in our banner instance is there's two different ways to run jobs versus baseline way, which is GJA PCTL. I've heard it called GJAPAL. It's kind of a weird name. What do you call it? Job submission. I actually didn't know the name of this form because I've always been used to just typing in the name of the job that I want in banner and I'll just take this right there for your parameters and run it. The other way here at Lynn Benton is kind of our own special homegrown way called Schwartz. Any of the jobs that we've invented here on this campus, we actually invented our own job submission system for them. The jobs don't cross over versus baseline versus Schwartz. So you have to know which direction you're going with things and to keep using. Someday, I'd like to get to a point where all of our net new jobs are actually all run through GJAPAL based on job submission. We're just not quite there yet. Now I'm going to go ahead and go through both of these so that it's a little less convenient because just talking about it, you can't quite see it. So let's go ahead and just jump right in. So in Banner, you can always get job submission down here for baseline or you can get to Schwartz over here. And really the instructions that you've got for the jobs that you're running might take you one place to the other. I'm going to go ahead and just run to the baseline where you first then we'll come back to it and then move that way to Schwartz. So GJAPAL, this is baseline. You can get to a list of all the jobs and processes that we have available to us and there are hundreds of them. Usually you know what job you want to run though. So you can either type the name of the job in here and I actually have a job that I chose last night to run. You can type in SHR, IAGE, some high-pence reports and pitch down into it and it'll pull up all the information. Or if you want to you can just type it in here. SHR, IAGE. It'll go straight there. Now within here there's three different blocks and you kind of want to go walk through them every time you run a job. How you want to get your output, your printer control, what parameters you want to run the job for and then you can actually save the parameter set. If you have different types of parameters that you run the job for so you don't always have to remember what they all are because this is actually a fairly simple job for parameters. Sometimes they've got to be more or more. Now printer control, the different ways you can get your output. I'll make a review of this at the end here so I'll kind of skim over a couple of different ways you can get output. One of the ways I like to do this is just database. We'll make sure you know what that is. Database just means that I'm not going to go out and get my output. I'm not going to print it to a printer. I'm just going to actually read my output inside paper. One thing to remember at the end of this is the submit time. Do you ever use this? Do you ever use the submit time? You can't actually tell better. Don't run the job right now. Run it tonight at 6 p.m. or something like that. It takes military time and there's a little note down at the bottom. It's hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, hour, in the code that you know, like 20603, or if you weren't quite sure what to put in there, you can always click on values. It'll bring up all the terms that I can choose from. It's all around this for the current term, like 20603. Next one down is required. I could put in multiple SIP codes if I want, but if I want to do it for all, it actually has more instructions down here. Put in a percent to be able to scrap all SIP codes. The next one is optional, so I'm just going to do a blank. And the one at the bottom is a required report format. I don't know what number three means, but it tells me down here at the bottom. If I put a one in there, it'll give me a hard copy. If I put a two, it'll give me a web output file. If I put in a three, it'll give both four. I'm just going to leave a three because that was the default that was in here. And then I'm going to ask the bottom in control page down through these different blocks, or next block. Now here, I can just hit save and it'll submit the job. Or I can actually save the parameter sets and give it a name, or whatever I want to type. And the next time I come in here, I could put that parameter name in here. When I control page down, all this information is saved for me to come right back up. I won't have to make any changes. I usually only use that name that saved the parameter set when I run in the same job over and over and over. I don't want to put it in the parameters again. It can be very useful, or it could be just let's just kind of answer higher running shots. And then I'll submit it. Don't have to put a description. And at this point, if you put a submit time, don't put a hold button. Don't click on the hold at the bottom because it goes in no man's land. Yeah, I would recommend never using hold. It basically says, you forget everything I just told you and it doesn't do anything. So I've submitted the job. The job is actually running against the database where it's already finished. We have a net new form where you can actually see the status of that. You can go back into the form and do the options. Show me. Go back into JJ to go to options. It's right here as well. You can type in the name just works or you can just click on this and it'll tell you whether or not it's running. And once that says complete, I can actually do my output. Okay, now it's running. I don't think I've ever found a baseline way to see this information. It's really useful to see if the job is running or not. We can see it on our end on the database. I don't know if there's a baseline way to see if the job is completed. All right, so it is run. I can either click view screen output because I had chosen database as my printer. Well, it may have been if the shell script was not set up to actually want me to do that. I can review my job output here. This is the baseline way because I had gone through it at LBCC, Schwab's way, probably didn't come up. This is the baseline way to see your output. If you didn't know your job number, you can always click right here and it'll show you a list of all the jobs you've ever run. Okay, and it brings up my report. Let's see right here. I can even print from here or I believe if I go to options, I have an option to open this up in a web browser where I can print to our copy and paste that sort of thing. One thing to remember if you're using database, this can get fault over time, especially if you're running multiple jobs a day. Occasionally, it's worth deleting your output and there's a place where you can just delete output and say, okay, and then it will appear. I ran through that real quick. It was a baseline way to run the job. Let's go look at the Schwab's way and then we'll come back and play with both of them and I'll show you that you can always do the output. So Schwab's, you can either type Schwab's at the top or you can click on this button on the right and going here will actually show you a list of all the jobs that we've built here at LBCC that you have access to. I actually have access to a lot of them, so I've got a huge list here, but your list may be different or bigger or smaller. And remember I had said the third character will tell you whether it's a process or a report. So you can see a lot of these, whoops, you can click on it and it takes you straight to it. A lot of these have P's. Sometimes it's an R. That's the difference between this is a process, this is a report in general. Everybody runs it all out. Or most of the people in here run it all out. It's all out. Yeah. You want to use that for an example. I was going to use GW order. Is there any appropriate data in there? It's not magic stuff. I don't know what it looks like. You want to walk me through the forever? No, you might not be set up. I don't know how to spell it. I didn't practice this one last night. The one I was looking for was function of Q. Are we going to run our new GW order? It's got the master SSN. GW order is a report that we built recently that helps us to compare two different records and data to see if it's a duplicate or not. So we can click on that. Last night I ran this for two IDs, so the IDs are still in there. It saved the last time, the parameters that I got in the last time. And so I want to compare this ID. It gives me some instructions. I want to put it here and click next. It gives me instructions again. It wants another ID and I've already entered this. And then you can choose where your output goes. I had chose database when I was in the baseline way. It's also called screen. You chose screen. It's the same thing. You can view your output inside there. Out here I'm going to choose no print. What that means is I don't want to print the paper. I don't want it to be viewable or banner. I want to actually just go out and get the file from someone. I'll say next. You choose when to run it. Similar to that submit time. You can choose to run it immediately. You can choose to run it some other time. If I choose to run it tonight, what time does that run? 10, 10, 15, 11, 15. It's late at night. I want to run this right now. It gives me a review of what I had just chosen and then I had submit. Again, we can always check our job stats and kind of watch for it to run. This job runs pretty quick. That's done. Now, if I click view screen, what are you going to be able to see? I've chosen no print. No, you should be able to see it. As I said, yeah, you can't see it here. But I can't get to it by going and giving the file. So we use a tool called Core FTP. And also understand that when you're in schwarps, just because it offers you a screen option does not mean that that job is actually set up for a screen option. So you might choose it. And if it hasn't been set up behind the scenes to do that, you're going to get that same error because of the process. But if you say no print, you still have files behind the scene. It's just not going to bring things for you into this part to see them. Yeah. And if these never behave in the way you don't expect, let us know. We can look at them, especially in the schwarps and when we built them ourselves, we've got to figure out what's wrong with them. We may have missed something at some point. So Core FTP, who used Core FTP? Who loves Core FTP? Kevin does. Actually, who knows what FTP is in general? Let's start with Jane. Jane gets a stone. It stands for file transfer protocol. All it really means is I've got files on one computer and I want those files on another. That's all it really is. So on the right hand, or when you're looking at this, on the left hand side of the screen is your computer, the hardware you're sitting in front of. And on the right hand side of the screen is whatever other computer you're looking at. Here, we're looking at the banner computer. Now, is that not customizable by a machine? So you could have a top to bottom. It depends on how your Core FTP is set up. So if yours doesn't look like this, don't freak out. It's because of how your Core FTP is set up. And pay attention to what you have in those little boxes where those highlights are, the blue are, because you could be opening them wherever you set your cursor and open stuff. You could be changing where you're sitting. So be cautious of, be aware of, of what you're doing. Right. And, and Lori, when she sets these up on your computers, she's got a set of defaults that you could put on computers. But that doesn't mean you're locked in all the time. Here, I'm actually looking at Devel. I've made a change here to the location of the other computer that I'm looking at. And there's also a filter up here that uses asterisks as a wildcard. I'm looking for any file that has my name in it, W-I-L-L-I-G. You can see that I ran this whole bunch of times last night. So when you run something, it always attaches your name to it? That's a default, the Lori said. Say, usually you should. If you went out and downloaded a Core FTP and did some of our defaults that you should have set up, they would just have a star there. Yeah. Did you mean when you run a job in Shorps, when you run a process? Yeah. Okay. And that's a usual. Right. So if I wanted to look just for GWR dirt, I can actually change this filter up here and I pulled back all the ones that I have access to. It also shows me the date and time that it completed. So we want to see the one for today, which is right here, right down here. So I can either drag this over here and drop it on my desktop and open it there. A lot of people, I think just view it directly from here. And I believe there's a setting that'll tell it to open up in your default, whatever you're going to see as we end. Sometimes it just uses notepad and that might be a setting that we can change. We can go and see this report where I compared Carl and myself. And we can tell that I'm looking at the information that we're not the same person. That's that's what their reports were. I do know I live here. So of course, you piece just a tool to go get the files that were helped by that job. And you choose no print to get this. You don't have to choose no print to get this. The files are always there. Right. Yeah. The file is always output. There's different file types. There's dot LIS, which is a text on that file. So you can look at it in a pad or word. There's some other text that in it. Dot CSV means comma separated values. News, et cetera. Text dot here, if there's commas in between each field, you can view it in Excel, which is really helpful. The PDF, we all know they'll react back to the PDF out, the sort of things. There's also that. So let's see, where are we at? I'm showing you once a baseline way of running a job. I'm showing you once how to run it in Schwartz. Let's go ahead and like to kind of walk through the different ways that you can get your outputs. We looked at core components. We can not do that again. We looked at database or the screen where you can view that information. There's also a different option, which I bet most people actually use. So if I went back to that job that I run baseline one, in this printer, not only can I choose no prints or database, but I can choose to have it go directly from banner to one of the printers. And these are also all blown up a little bit. So it's hard to read. There's a lot in here. There's printers in our office. There's printers in the registrar's office. They're set up specifically to receive data from the data. If you really want to have paper, you would want to choose one of these. Or if you need to give something to the Betton Center and you don't want to send it in campus mail, you can send it to the Betton Center printer, as long as they understand it's coming. As long as they know it's coming, you bet. And you know what's on that information. Well, I don't even need to know what's coming. One of the printers is falling. And if we ever need to set up a new printer for one of these, we send that information to Mark, he can work across and they need to set up. That's not that big of a deal. One that we do want to point out, though, is PDF print. So PDF print is kind of a weird mix of no print. And I want to get my file out at CORE-STP. A PDF, if you want to split that, then you have to print it to a PDF and put it to a file. It's kind of a weird way to say it, but we have to do the same thing where we're in Word or any other area of the internet. We choose a PDF printer. So if you want your report to come out readable and adobe, you would choose this. And let's walk through that. And what catches me up in this is that when you're choosing PDF print, you're not choosing a form. You're choosing a printer. Right. It's so, that's the point where you always catch up on it. I'll catch up, Lester. One more cup of coffee and I'll be there. Okay. You can always watch and wait for it to finish. Because I'm in a development instance, I'm talking to Carl because in production, you choose PDF print and it just comes out. So you can know which parts to take to file. In the end of our development instances, we actually hold back on print jobs. We actually request to have them released. That's what Carl's doing right now. So now that the job is printed, we can go out to core FTP. They can refresh it. It's not to get more dirt to change my filter. I'll just look for anything that I've ever run. And the name of that job was S-H-R-I-A-G-E. There should be a bunch to start off with. Yeah. Do it. Do the work on date. I could. You can sort of do this to catch you. Yes, sir. I just sorted it backwards. There you go. This is the one I just ran. And I still have my text file, my .LIS. I wanted to look at that. But I also have a PDF and I can open this up. And it should bring up the Reactive App. And this is another piece that has yet to help getting set up. And it doesn't come out in a minute. There's a core FTP in this. Lori is doing that now. Yeah. So you can see here is things in PDF and then print out the 1 or 2 pages out of 1,000 pages of what came out of the printer and things like that. Right. I know finances is a PDF quite a bit. Because a lot of their reports are huge. And they only use the one page in general. So rather than printing what you had to say, it's going to say just print the PDF, put it in your file, and then grab the one last page and print out the page. Or if you have to, we know what you created and how you're using this. I don't know why. I think it depends on what you're going to use it for. Oh, I didn't see that. Sorry guys. I'm a big fan of PDF print and you won't pay for this. Are there any things you'd like to see me walk through again? So I'm not going to choose that. I threw a lot at you. Otherwise, this is about how far it is. I mean, it's knowing the difference between a process and your report. Why am I running this job? And then how to run it, how to get your output. It's all the job solutions we wrote about. So I think the jobs for what reports that are in Schwartz are they in the baseline one? Not right now. They will be. No, they will be eventually. They are not now. So if I went here and typed in a Schwartz job, like GWR BERT, it's not going to bring anything up. Because we haven't done the baseline setup on our own. We've done the setup in our own clean wrote system. We've brought these new jobs. That's a transition we're going to have today. And when we actually start to make that transition work, you guys know. Because I think it would be a really cool difference. We run it there. And then senior parameters in the baseline way. And then none. And then everything in the clean system. I don't think it's confusing having two of those systems. Good question. Jane. All my documentation from a person that had a report me said that when you run a report, you should always check the same parameters set button, even though you don't put a name on it. So I'm hearing that you don't need to do that. You have to. And you can't get any further. Oh, you do have to always check that. OK, so it's true. Regardless of whether you really are going to associate with a name or something. Right. So when Gabe put in test, he could run another job next, PHP cal for something. And it's going to get rid of all these parameters. Right. You could be running something over and over and over and changing parameters. You could still go back to test and get whatever you did at that point. Right. So we needed to prove down the road or maybe have something you run on they once a year for a certain way in a certain way. And you want annual reporting for something. You could create an annual reporting. Right. Same set of parameters and go back to it. And then run things monthly throughout the rest of the year or something. Right. Just to run a job, you don't have to hit this check box. This just saves the parameters you put in. Yeah, that's what I was asking. My notes say that you always have to submit it. Yeah. You have to submit it, but you don't have to save the parameters. You don't have to put that. You don't have to put this check box right there. You don't have to save them. They won't have to save them anyway. But just save them there for the next time you run them. I put in 2016-02. I can go down here and I save the parameters and I don't put anything in. Next time I come in, this will become my default. Yeah, it did automatically put those in. But if you don't click that save parameter and just hit save, it will just run. That is still processed. Okay. Yeah, just run it. Okay. So now if I go in again, 2016-02 is there. Yeah. But if I go in as test, the one that I did name, 2016-03 is there. So it just gives you the ability to control default values that are in here. Right. It's not essential to running it. It's just a matter of what you want to save it in. Right. And this one might not be a great example. It can only change one parameter. But if you've got a job that has some 30 parameters, you have to remember what every single one of them are. You can find the job. It's worth saving it or even saving a few different versions of it so that you can just remember to run that one name. So show us how to run it without getting to save parameters. Go down. Go down. Go on. Yeah, I'll come in with that even in the name of the parameter. So just my defaults. And I just hit put. Just in settings. And it submits it. Yeah. Okay. That's not my understanding why we use it. Yeah, the only thing down there is to save your defaults. You need to be in that bottom block to submit it. Yeah. To save it. So it's either click that button or go to the top and hit the save button. Okay. Brett, that's good clarification. You do have to have your cursor down in this block to save and submit your job. Yeah, because of this right here. That's it. You don't have to use anything else down here. And we don't recommend you use it. But if you're down there, you just click on the same thing. It may just be the person before you wanted to make sure that what they were doing their own work, they always had the last last time they ran the job. Right. It was what that saved for them. Yeah. And I actually understand why now because nine times out of 10, you're going to want the next week just like want to do lines. But I always thought it was like you had to do it no matter what. So it's interesting to know that you don't. The big question for this crew, because I don't know the answer to this, Schwartz saves the last parameter set that I ran, but is there a way to save different parameter sets like this? We don't have that ability at Schwartz. It just saves the last time I ran the job, whatever I ran with, that will, that's what it's going to bring the job up. It can be your life easier. I know I used to run hundreds of jobs for missions on this. I mean, having different sets for different types of tape loads and whatnot. Yeah, I'm using it for academic standards. So when do I want to use it and how do I want to use it? So this other question, I think we're kind of at the point where it doesn't have to be about job solution. We can really ask anything. Is it super clear? Are you going to play around with it a little bit when you get back? Can you go over a little bit where you would find the documentation on what different fields are? Actually, that's awesome. I was going to do that and I forgot. Thank you, Jay. So what if you don't know what the job is doing? You don't know what the parameters mean and the instructions aren't really that clear. It's a baseline job. There's awesome documentation out there in the band office. Oops. Come out here to our groups and docs. And for example, Banner students. There's a report for a process or something that's something that I want to run and I'm not quite sure about it. Or even if I want to learn all about everything else that I could run, there's usually reports of handbook. If you come out here, it'll tell you anything and everything about any report you want. So like, I wanted to find out about the SRE, which is not a report. It's the electronic app verified load process. This is how they take applications that were submitted on the web and they push it into silos and other areas of Banner. I can go to this and it will tell me anything and everything that I want to know about that job. All the way down to what Jay was saying, what each one of the parameters does or not required, what the default values are. Using these reports and books can be extremely powerful for you, especially as you're learning Banner. And if you're not able to find a report handbook or a description of one of the jobs you're looking for, always ask us if we can help you to find out maybe see a hub or figure out why it's not documented so well and get some straight answers. These handbooks are awesome. They're pretty amazing. Once you get used to looking at them and searching, like I just searched for this one job, you can drop the information up to half a minute to read out. I think they even have like a sample output. Most times that doesn't look like that one for that. I'm not to the next job. Sometimes they do and they'll actually show you where it's going to look like on the output. That's all the way down. Do you think so? Like you above it sometimes? No, not that one. Great question. Thank you for reminding me. Now, if you're not in baseline and you're actually playing on the Schwartz side of things, we have tried to be good about creating details for you. So when we go to Schwartz, there's little details all of it. And if it's marked with a Y, then that means there's actually something within it. So if you were to highlight one of those, cancel all that, highlight one of the details, see details at the bottom. Now, I do not guarantee that that is actually up to date, but it could give you some information on the job itself. Right. It can be very helpful. You'll notice that they're not as common. So if you want to run a Schwartz job or you're not sure what it does or anything, you want to work with the program, just because they can actually trace through the code and figure out exactly what it's doing and why. Usually we have notes behind us that help us. Usually. We like that word. You have a question? Any other questions? Oh, yeah, that's that. Is that from your work in December? So right now, if you want online help, you go right here and it takes a few of these and this can help. Technically, that's not baseline. There's a lot of help that van provides, but we've never installed behind the scenes. They would tell you everything about the baseline form that you're in. Sounds like Mark's been doing a lot of research into this and that should be available in the future, for some day in the future. And we'll let you know when that becomes available. Because that also can be useful for finding out how some of these things work. Mark's been doing a lot of work on this in this past week and getting pretty excited. It might actually be implemented in the future. What is ESM? ESM is Ellucian Solution Manager. It's a tool on our side that helps us make sure that our databases are up to date. That they're set up in a way that Ellucian expects that helps us turn on new tools, like seeing it sign on, ban on. It will be a level up for the entire campus and something Mark's been working on for about a year and a half. That platform is going to be what Ellucian is going to use across the board for all of their products, professionally, which is why it's not called Banner Manager or anything like that. They just started with Banner because that was the biggest piece that everybody's ever seen. So what it will do is I'm using it in two ways. One, just finish tying it into our standby environments. And later on today, I should be able to actually use it to update our standby server to what production is now. And if that's successful, I'll be tying that into our current production server, the one that everybody else uses, and start running that for the next week. The other side of that is the new system that we're building to migrate over into what is now called Banner 9. Everybody's calling it Banner 9, Banner XE, whatever. That system has been built, ESM is tied into it, and it is now, I'm now troubleshooting various pickups as it is installing Banner into that system. Hopefully, my timeline, personally, I think maybe what I've talked about this is that we'll have it up and running. Sometime use this term or next, and start doing some serious testing next term and summer, and start rolling out new look of Banner involved on the system. The projects we've been working on and communicating in the past few years, so I'm going to start paying off in the next six months to nine months to a year in the future. The painful baseline, baseline with Banner, we've been going through, we'll start making things easier to operate Banner 9, get new tools, put in place like reworks. We saw many more projects to go. We're not nearly done. ESM makes it a sign-on, more realistic. That's something that we're going to be working on, just as soon as ESM is up and running. Banner 9 is a leap forward and loaded and looks and feels and behaves. It won't feel like error strings from 1990s. It will actually feel like an application that was developed after the turn of the century. All the functionality we love in Banner 8 is going to be there. It starts to open up a whole lot of other possibilities like having a mobile app that allows you to get a new Banner or a degree more, starting with other tools that we've run alongside all that. Turning on ISSM, the International Student Scholarship Management Tool. It's part of that. It's a pretty exciting time in my opinion for Banner. A lot of the things we've been just dedicated to for the past year, a year and a half more, we're going to start actually showing to you real quick. It's a good project update. Other questions, we've got about five more minutes if you want. Before there are any more questions, you can shut her down. These recordings will be available online at the YouTube page. I slacked off last month and I've now put the official service going up, but I want to do that at the same time with the three states of Nepal. I'll be really careful now. Show them what CASTing looks like right now. No. If you ever need to get all of us, there's our email address. It fits the whole team. And if you want to have a short link to our YouTube site where all the other recordings of these sessions are at, there's a bit link right there. Thank you for coming. And let us know if you have ideas for future Banner bunchers.