enterpriseschedule getting started with...

EnterpriseSCHEDULE

Getting Started with

Banner

Installation and User’s Guide

Revision: Version 7.7.xx

Release Date: May 5, 2017 ISE Ban Module 4xx

User’s Manual Page ii

The information in this document is subject to change without notice and should not be construed as a commitment by International Structural Engineers, Incorporated (ISE). ISE assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No part of this publication may be reproduced, stored in retrieval system or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or otherwise - without the permission of ISE. ISE Inc PO Box 836 Hawthorne CA 90250 (310) 643-7310 E-Mail: [email protected] Website: http://www.i-s-e.com

Copyright © 2017 ISE Inc All rights reserved

mailto:[email protected]

http://www.i-s-e.com/

User’s Manual Page iii

EnterpriseSCHEDULE Getting Started with Banner Installation and User Guide

TABLE OF CONTENTS

Page #

Chapter 1 Introduction to the EnterpriseSCHEDULE Client 1

Browser compatibility ....................................................................................................................... 1 Getting Help using the EnterpriseSCHEDULE desktop Client ........................................................ 1

Chapter 2 Creating a Banner Job using the EnterpriseSCHEDULE Desktop Client 2

The Basic Banner Job Templates ...................................................................................................... 6 Customizing Banner Template jobs .................................................................................................. 6 Understanding Banner parameter save sets and Banner Jobs .......................................................... 12 Defining a new Banner Object ........................................................................................................ 12 Creating a parameter save set for a Job or Jobs............................................................................... 12

Chapter 3 Creating a Banner Job Stream 15

Chapter 4 Example Banner Job streams 34

Award Letters .................................................................................................................................. 34 File Review and Verification .......................................................................................................... 35 Missing Information Letters ............................................................................................................ 36 FAFSA_Dataload Download ......................................................................................................... 37 FAFSA_Dataload Merge ................................................................................................................ 38 Application Data Load Job Stream ................................................................................................. 39 Financial Aid Data Load ................................................................................................................. 40 Financial Aid Finance ..................................................................................................................... 41 Daily Finance .................................................................................................................................. 42 Daily Foundation and Enrollment Finance ..................................................................................... 43 Sharing Jobs and Job Streams ......................................................................................................... 45

Chapter 5 User/security management and segregating users/functional groups. 46

Users access rights .......................................................................................................................... 47 Private User within EnterpriseSCHEDULE .................................................................................... 48 Use of a Default Job and propagation of an OS submit user ........................................................... 48 Group definitions ............................................................................................................................ 49 Oracle/Banner name space .............................................................................................................. 49

Chapter 6 Creating customs includes with your site’s added details and creating additional job prototypes. 50

Custom job command includes ....................................................................................................... 50 Creating additional job prototypes .................................................................................................. 50

User’s Manual Page iv

How to make SQL*Plus an option on the “Submit” property page ................................................ 51

Chapter 7 Commonly Used Job Stream (workflow) Concepts. 54

Using a job as building block .......................................................................................................... 54 Managing the flow of your tasks, the Job Stream ........................................................................... 55 Propagating global data through the Job Stream ............................................................................. 57 Managing the Job Stream across the Enterprise and multiple hosts ................................................ 57

Chapter 8 Example job template 71

User’s Manual Page 1

The EnterpriseSCHEDULE Client is a desktop interface that lets users connect and manage one or more EnterpriseSCHEDULE servers. The servers are located on the host or hosts where your jobs run. The client connects to a singular or multiple Schedule server host(s), such as Linux, UNIX and Windows. In the case of using EnterpriseSCHEDULE to automate Banner, the host(s) EnterpriseSCHEDULE server must be accessible to an ISE IIS Web Server in order for the complete extended ISE Banner property pages to be displayed. Please refer to Appendix 1 – “Installation of the ISE EnterpriseSCHEDULE to automate Banner” before getting started to ensure all installation steps for Banner automation have been performed.

Browser compatibility The extended Banner property pages used by the EnterpriseSCHEDULE Client require a recent browser. The following browsers are supported: Internet Explorer 9 or greater Chrome 3.0 or greater Firefox 35.0 or greater

Getting Help using the EnterpriseSCHEDULE desktop Client

After installation of the EnterpriseSCHEDULE desktop client there are a set of documents available under the EnterpriseSCHEDULE folder. Online Help is available at support.i-s-e.com. In addition, there is a set of documents online to help you get started using Schedule. Lastly, the EnterpriseSCHEDULE client includes a “Help” with complete EnterpriseSCHEDULE help.

Chapter 1 Introduction to the EnterpriseSCHEDULE Client


After installation of EnterpriseSCHEDULE and the Automate Banner kit, open an Explorer view within the EnterpriseSCHEDULE Desktop Client by left mouse clicking on the 3rd icon (hovering your mouse over the icon will display “Explorer”). Expand the folders and browser a few of the folders. You may want to browse through the folders “/ban_controls” and “/default/ban” as they are components of the Banner Schedule module.

1. Create your first test job by right mouse clicking on the host name below “Network

neighborhood” and select “New Folder”. Give the folder a name such as “/ban_demo”.

Chapter 2 Creating a Banner Job using the EnterpriseSCHEDULE Desktop Client


2. Inside this folder create a job using the built-in Schedule job template tool and select a

Banner Job template such as: right mouse on the new folder selecting “New Job from

Ban Banner C job template or Banner Cobol job template”. Give the job a

meaningful name such as BanTest1 and BanTest2.


Note: In naming jobs it is common practice to include both the banner program name

and the parameter save set used in the job. Such as job name

glbdata_award_ltr_1ST_em. When stringing the jobs together in a job layout (workflow)

you can and will arrange the jobs into a proper order based on the task flow. However,

when viewing the jobs in the explorer view they are listed alphanumerically. Many times

a step number is added to help view the order of jobs.


3. After creating your first job such as “My_first_ban_job” it’s important to select the

property pages and work through the properties of your job.

4. After working through the properties of your first job, it is then best to create a Cobol job,

C job, Sql job and Java job (and for some schools a Sqr job). By doing one case of each

of the various types of Banner processes you should then be able to run all Banner

programs and scripts available to you within the Job Submissions library.

5. A later chapter will expand on creating a job stream and using dynamic runtime variables

sometimes referred to as override values.


The Basic Banner Job Templates After creating your first Banner job(s) such as a Pro Cobol job or Pro C Job, you may want to go back through each of the job templates taking note that your site’s custom details should be written within the includes “/default/Ban/bani_ban_custom_*” as later ISE upgrades may over write any existing jobs and includes. Remember the jobs “/default/ban/proto_*” are your templates. There are a couple of objectives in using job templates. The first time through in testing, select job property page parameters that will work. Then taking note that each time a new job is created from a template the fewer fields you have to change to deploy the future jobs the better the template is. If you chose to create your own templates place them in another folder under “/default/” and/or pick a naming convention that won’t conflict with an ISE’s naming convention. A popular naming convention puts a school’s acronyms into the job template name such as “proto_xyz_sql_job”. Example: You may look at the basic ban job templates and think you are going to deploy your Finance jobs using user “baninst1”, in addition you are going to deploy your Financial Aid jobs using “Faisusr” and lastly a generic set of analyst jobs are going to be “user” specific. Each of these functional areas will have several different field settings from user to output location. Such that you may want 3 sets of job templates for each of the functional area’s jobs. As a result, presetting as many property page fields early on in the templates will speed your job deployment later on because you won’t need to manually duplicate updates in the property page fields.

Customizing Banner Template jobs In summary here is a set of customizations that you may need to performed. a) Walk through your test job’s property pages and make sure the Banner environment is

correct for your environment.

b) Secondly update the templates of all your Banner job templates under the path

“/default/ban/proto_*”. Decide if one set of templates will work or if you need to create

multiple templates for different functional areas. The reason being is a job created from a

job template has its property pages details propagated to the property pages of the newly

created job. This can help save you time editing each field with every newly created job.

Note: By default the “Submit property page” that defines OS user the job will run as, is one

field that does not propagate to a new job from a job template. See chapter 5 for more

details.


Note: If you choose to create additional Job templates please contact ISE for an overview

on ISE Schedule’s Job prototypes, Schedule’s Job Include pieces and Schedule’s

Preprocessing .

c) Walk through of property pages; select a template type such as Cobol.


d) Add in your Banner user and your parameter save set. Then select if you want Schedule to

scrape the log and/or lis file for additional text errors that might occur.

Note 1: Refer to “Understanding Parameter save sets and Banner Jobs” below if you are

not familiar with Banner parameter save sets.

Note 2: In jobs “/ban_controls/bani_scrape*_keys” the list of key phrases can be viewed

and modified. By default Schedule captures the program’s runtime completion status and

scrape is an additional error check.


e) Decide if you want any output moved to a location in addition to going to the standard

output directory (share) location.


f) Decide if you want and/or need to use any run time parameters that will be merged in with

your static parameters from the parameter save set.


g) The Oracle controls can be updated by hard coding the values, using the default set of

variables in”/ban_controls” or using variables in the local or parent folder.

Note 1: Only a user with privilege can view the username password. This information can

be held in a variable, a hidden credential file or an Oracle Wallet proxy BANJSPROXY.

Note 2: Reference Appendix I, steps 6 & 7 for the default setup of these values.


Understanding Banner parameter save sets and Banner Jobs

This section explains how jobs are setup and run within the Banner system. The Schedule Banner jobs you define are calling processes from the installed Banner library of objects. These Banner processes are a collection of programs and scripts that typically reference a static set of parameters saved in a table, called a parameter save set. In addition to the static parameters a Banner process may require runtime dynamic parameters. Many times these runtime Banner parameter values are needed for multiple jobs and can be defined as Schedule Variables, making them accessible to all Schedule Jobs under the same directory (folder) or directory tree. You will need to define the Banner process and user specific parameters, such as the parameter sets you have saved in Banner, in your Schedule Job.

Defining a new Banner Object

You can define a new Banner Object (add to the Banner library) with the Object Maintenance Form (GUAOBJS), which will create a new object for the job into table general.gubobjs. The System field contains a system indicator code from the System Indicator Validation Form (GTVSYSI). You must use one of the delivered codes or you can set up W, Y, or Z on GTVSYSI to use with your custom forms. The Data Extract Option field determines which extract options are enabled on the Help menu. The option can be enabled for both key and data blocks or data blocks only, or not enabled. SunGard Higher Education delivers Banner with the extract option enabled for all validation forms. Your system administrator can use this form to enable the extract

The User ID is BASELINE if the object was delivered with Banner; these objects cannot be deleted. The User ID is LOCAL if the object was developed at your institution.

Creating a parameter save set for a Job or Jobs

Use the Process Submission Control Form (GJAPCTL) to save parameter sets. There are four main blocks for the screen GJAPCTL. The Key block identifies the Banner report you want to submit for processing. In the Process field enter the report name you want to submit for processing. If you have entered the report name in the General Menu screen the name will already be populated. If you have used this report in the past, and saved the defaults under a unique name, enter that name in the Parameter Set field. You can have more than one set of defaults for the report, each with its own name. Using job parameter sets lets you run a report with different combinations of parameter values and saves it for future use.


The Printer Control block allows you to specify the print settings for the report. Should you not select a printer but select ‘DATABASE’ you can preview the report before you print. This feature also allows you to save it and print it using Microsoft Word. The Parameter Values block contains several fields for the values of your reports based on the parameter available. Parameter entries may be ‘Optional’ or ‘Required’, and ‘Multiple’ or ‘Single’. If the parameter is ‘optional’ the parameter may be left blank or a value entered. ‘Required’ means that an entry must be entered or select what has been defaulted by the system. ‘Multiple’ allow you to use the same parameter on multiple lines. ‘Single’ allows one entry to be made. The Submission block allows you to save the parameters you selected and to name it so that it can be reused. You can create a report several times and name it differently based on the parameters you selected. By placing a Check in the Save Parameters field box indicates the parameter values should be saved as user-defined defaults for the report. If you want to save this as an unique set of defaults for the report, select this check box and enter the name and description of the job parameter set in the As fields.

When you submit a job on the GJAPCTL form, it invokes the ISE stored procedure gjob_parms.sql to build an object with the job name and its parameters and get the reference number to that object, the one-up number, that is needed to run the Banner process defined in the Schedule job. The typical ISE Banner job will reference your parameter save sets. Note: a parameter save set is unique by “process name”, “user name” and “parameter set name”.

Key Block

Printer Control Block

Parameter Values Block

Submission Block

Click here to save the parameter set.


This is an example job stream creation walk through of a Financial Aid Data Load. Only the first 8 jobs are depicted. As an end user you should be able complete the entire task of building your school specific 40 to 70 jobs yourself after you walk through the creation of these first 8 example jobs and couple each of them with downstream initiates as the chore of creating additional jobs is the same. Note: Importing “isebandemo.schedule” will create the same jobs in folder “/ban_demo_dataload”. As an exercise follow the steps below creating “/ban_demo/dataload” compare the two sets. Refer to Appendix 1 step (5) if errors are occurring on import.

1. Create your new folder by right mouse clicking on the host name below “Network

neighborhood” and select “New Folder”. Give the folder a name such as “/ban_demo”.

2. From folder “/ban_demo/” create sub folder such as “/ban_demo/dataload”.

3. Inside this folder “/ban_demo/dataload” you will be creating jobs using the built-in

Schedule job template tool by selecting a Banner Job template.

4. To create each job you will right mouse on the new folder select “New Job from

Ban {banner process name} template”.

Chapter 3 Creating a Banner Job Stream


6. In general you will be creating a Cobol, C, Sql, Sqr or Java Job. However at times you

simply need to run a generic Sql script to clear rows or something and you don’t want to

install it into Banner and you don’t need a Parameter Save set. This job stream has a

couple of those types of jobs within the stream. For job 1 right mouse on the new folder

select “New Job from Ban Banner Sql include job template”.

7. Right click on the job and select “rename” and call it “001_1516_roainst_null”.


8. Update the fields “Program Name:”, “Additional Data 1:”, “Additional 2” the same as the

screen capture above making sure there are no typos.

9. Create a generic Schedule Job by right mouse on the new folder select “New Job”

10. Right click on the job and select “rename” and call the job

“001_1516_roainst_null_script.”

11. Right mouse click on job “001_1516_roainst_null_script” select “properties”. Then select

the property tab “Commands” and cut and paste the scripting below into the commands:

select count(*) counter from robinst

where robinst_aidy_code = ((Aidycode));

update robinst bt

set bt.robinst_current_period = '201611',

bt.robinst_current_term_code = '201611',

bt.robinst_aprd_code_def = 'FHMFWS',

bt.robinst_sapr_code = 'X',

bt.robinst_infc_code = 'EDE',

bt.robinst_treq_code_appl = 'FAFSA'

where bt.robinst_aidy_code = '1516';

commit;

12. Select “Apply”. Then select the “General” tab and enter “Custom Sql Roainst Null Script”

into the “Comments” field. Select “Apply” then “OK”.

13. Right mouse click on job “001_1516_roainst_null” and select “properties”. Then select

the property tab “Commands” and select “preview” to confirm the job pieces work

together.


14. Exit out of those dialogs and create Job 2 with right mouse click on the new folder select

“New Job from Ban Banner Java job template”.

15. Right click on the job and select “rename” and call it

“002_1516_rctpxx_fh_dataload_pt1”.


16. Update the fields “Program Name:”, “Parameter Set User:”, “Parameter Set Name:” the

same as the screen capture above making sure there are no typos.

17. Go into Banner Process Submission Control Form (GJAPCTL) as described earlier and

create the parameter save set FH_DATALOAD_PT1 for process rcptp16 as user

“baninst1”.


18. Create an initiate from job 1 to job 2 by going back to the standard property pages of job

“001_1516_roainst_null” select the “Connections” tab click “Add” browse to the second

job “002_1516_rctpxxfh_dataload_pt” then click more and select “Severity level is”

“Success”. Last screen of the below sequence shows the Html style property page. You

will do this for every downstream job. Initiates can be sequential or in parallel depending

on your workflow needs.


19. Create Job 3 by right mouse clicking on the folder selecting “New Job from Ban

Banner C job template” and then rename the job 3 to

“003_1516_rcpmtch_fh_dld_pt2_1516”.

20. Fill in the details as listed above and you will be repeating steps (16), (17) & (18) with

slightly different details updating 3 fields with rcpmtch, baninst1 and FH_DLD_PT2_1516

and then create the downstream initiate by going back to the previous job.



Banner Java job template” and then rename the job 5 to

“005_1516_rnpfm16_fh_need_calc16”.


slightly different details updating 3 fields with rnpfm16, baninst1 and FH_NEED_CALC16



Banner COBOL job template” and then rename the job 6 to

“006_1516_glbdata_college_code_fh”.



slightly different details updating 3 fields with glbdata, baninst1 and

COLLEGE_CODE_FH and then create the downstream initiate by going back to the

previous job.


25. Staying in the extended for job 006_1516_glbdata_college_code_fh as depicted above

select the property page “Banner Overrides” as we need to add a dynamic runtime

parameter to this job.

26. The Banner rules for runtime override and dynamic values when supplied to the gjbprun

table to be merged in with your saved parameter set are “column,value,tag” where

column “88” is a special case dynamic column value. Within a row of the gjbprun table

column is the location, value is the value and tag is a value description that must match

as described within your given saved parameter set.

Note 1: It’s very helpful if you chose a constant naming convention at your school for

“tag(s)” with your parameter save sets as this will save you runtime failures if there is a

mismatched and then you won’t to track down the issue. Example: for “Aid Year Code”

pick a style Aidy, AidYearCode or whatever but keep it the same.


For the definition of the override strings, if you look at the pulldown for “Override 1” on

this property page, Schedule allows you several choices; Such that you can hard code

the string, you can look it up in /ban_controls (typical recommendation), you can look it

up in the parent folder and you can look it up in the local folder.

Note 2: Schedule does several passes in its preprocessing evaluation and expansion of

includes, variable and parameter definition. So a simple variable ((xxx)) means look for

“xxx” in the local folder and ((/ban_controls/xxx)) for “xxx” in folder “/ban_controls))”.

Selecting “override 1” predefined string “((/ban_controls/override1))” which will

preprocess to “88,((/ban_controls/Aidyear)),Aidy” and defined string

“((/ban_controls/Aidyear))” will preprocess to “1516” which in the end will preprocess to

“88,1516,Aidy”. Such in the future when you want to “1617” you just need to update

variable “/ban_controls/Aidyear”.

Note 3: In the commands of “/default/ban/bani_ise_gjob_params” if you uncomment,

remove the “#” from the two debug lines at top it will put the stored procedure loading of

the gjbprun table into verbose and you will get a listing of every loaded parameter both

from the parameter save set and from the override values. A large number of schools

like to have this always enable so they can easily review the parameters loaded in their

job log files.

# Uncomment the next two lines for debugging of gjob_parms

#debug_flag="Y"

#export debug_flag




“007_1516_glbdata_col_code_both_f”.



slightly different details updating 3 fields with glbdata, baninst1 and

COL_CODE_BOTH_F and then create the downstream initiate by going back to the

previous job. In addition perform steps (26) & (27) on this job.



“008_1516_rorpost_null_collegefh”.



slightly different details updating 3 fields with rorpost, ((Aidycode)) and COLLEGEFH


Note: ISE provides this simple but handy frequently used Sql procedure. The details of

script are contained in the commands of job

“/default/ban/banner_rorpost_null_category_script”.


Banner C job template” and then rename the job 9 to “009_1516_rorbpst_rorbpst1516”.



slightly different details updating 3 fields with rorbpst, baninst1 and RORBPST1516 and

then create the downstream initiate by going back to the previous job.


33. Lastly it’s best to create a layout depicting your job stream. It is possible to have more

than 1 layout depicting all or part of a job stream. The layout(s) can display jobs, variable

and be annotated with text, color and other useful objects. Right mouse click on the

folder selecting “New Layout”. Then right click on the layout selecting rename and call

it “Dataload_fh”.

34. Double click on the layout “Dataload_fh” to open it. Click back on the explorer view

selecting the [Job] objects. Also, select pulldown “Window Tile”.


35. Lastly drag and drop the jobs and variables into the layout. Notice that when you are in

the layout dialog you can select the icons on the right boarder to change the property

behavior of the mouse.


Award Letters The Award Letters job stream generates award letters populated with applicant information from the

Banner Database to notify students if they received financial aid assistance or not. There are dynamic

runtime variables that are used across the jobs, Loaddt, Aidycode and Termcode.

Chapter 4 Example Banner Job streams


File Review and Verification The File Review and Verification job stream pulls up students’ tracking requirements for review and verification. There are dynamic runtime variables that are used across the jobs, Loaddt, Aidycode and Termcode.


Missing Information Letters This Missing Information Letters job stream generates and populates letters with student information from the Banner database.


FAFSA_Dataload Download This is part one of a two Job streams. Part one downloads the FAFSA government student financial aid records.


FAFSA_Dataload Merge This is part two of a two Job streams. Part two merges the FAFSA downloaded government student financial aid records across two financial aid years on a daily scheduled basis.


Application Data Load Job Stream This is an Application Data Load Job stream that was implemented at a University and run on a daily schedule.


Financial Aid Data Load One of the more popular daily tasks schools chose to automate. This is one of the many versions implemented.


Financial Aid Finance It is easy to build your own new jobs with your own set of parameters.


Daily Finance This is another popular daily task that schools automate as the manual procedure requires many hours each week.


Daily Foundation and Enrollment Finance Variables are used across the set of jobs and are easy to modify when the term changes.


Sharing Jobs and Job Streams ISE has a built-in extract/load feature to copy database objects between hosts. This allows Jobs and Job Streams to be extracted and then imported from a test system to a production system, or set aside a backup and share solutions amongst Schools.


Chapter 5 User/security management and segregating users/functional groups.


The following discusses OS name space both on the host name space such as Linux and the desktop client Windows name space, and then the Oracle/Banner name space. In addition how the mapping of Oracle users to an OS user is done to allow automation to occur while still maintaining security. Finally discussed is how to use an Oracle Wallet {Oracle name space proxies} to run both functional area jobs and individual analyst’s jobs.

Users access rights Users of EnterpriseSCHEDULE (ESchedule) connect (log) into the ESchedule server process to perform their tasks of automation. Typically this function is the automation of the many individual tasks a user performs within Job Submission along with any other repetitive task such as moving files. There are two types of logons whereby you either (a) map/proxy to an OS account where the ESchedule server resides or you (b) map/proxy to a ESchedule private user that is limited to the group membership controls. To (a) logon to ESchedule in the default behavior a user who is logged onto their Windows machine starts an ESchedule GUI client session and in connecting to ESchedule they will be authenticated by ESchedule and its host machine such as a Linux host. This authentication is in the form an OS username password challenge. Note, the password is transmitted across a private tcp port connection, the packets are binary and the password is encrypted. Upon authentication a proxy between the user’s Windows account and ESchedule host account is made. Upon a valid authentication, the user has the rights and privileges within the ESchedule environment that are the same as the host user they are mapped to. The proxy is held within the ESchedule server’s database. Upon a successful logon a user record is held within the ESchedule server’s database. In some (b) cases giving an ESchedule user an OS account on the ESchedule host machine is not preferred. In this case ESchedule allows the creation of private user that by default has no privilege or access on the host. The ESchedule system administrator must add Access Control mappings for the private user’s account. Typically this is done by creating groups that contain access mappings to folders and jobs. The private user is given a membership of a group(s) that allows him/her to perform his/her mission. Typically a private user account is created with a preassigned password with the attribute of “password change required”. The logon sequence from Windows to the ESchedule host presents the same type of challenge and a proxy is created. Typically groups are created to assign access to a functional area with read (submit), write and delete privilege. As an example you may create a group Finance_Operator with read (submit) privilege only to the Finance functional folder. Then create a group Finance_Admin with read, write, delete privilege only to the Finance functional folder. You would repeat these steps for other functional areas such as Finaid and Admissions. Then users such as private user JohnDoe would be allocated the group access such as Finance_Operator. The private user can not log directly into the host machine but would be able to run jobs within the Finance scope. Note: ESchedule runs jobs as a given user on the host. In the case of using a private user, an OS host execute user is needed and used. No user record for the execute user is created; the private cannot logon as the OS execute user, and the private user has limited scope.


Optional security logging can be turned on to track submissions and modifications to the ESchedule database. For private user verify the following values are correctly configured in the ESchedule parameter file. -AUTHENTICATION_METHOD -USE_DEFAULT_USER -USE_DEFAULT_LOGPATH -ENABLE_USER_VIEW_LOG When running jobs through Banner’s Job Submission most users typically don’t concern themselves with the concept of an OS user who the actual Job process is run as. Job Submission runs your job as an OS user for you and your Banner/Oracle user is just another supplied parameter to the OS process. Within EnterpriseSCHEDULE you can keep the OS user concept very simple by having your Sys Admin pre-pick an OS user for the jobs to run as. In addition, you can create private users for access login in EnterpriseSCHEDULE that map to the users in Banner/Oracle. This allows you to simplify user management without the addition of adding another OS name for every Oracle name.

Private User within EnterpriseSCHEDULE

You can have a Sys Admin create a private user within ESchedule that maps to a user’s Banner/Oracle account. As the Sys Admin, simply go to the /syscontrol/users and select “new user”. The first time a private user logs into ESchedule they must reset their password. Because the private user does not have an OS password file for log location and other details it is important for the Sys Admin to create a “default” job in the user’s home folder and set the default job’s “submit user” to an OS execute user that enables the running of Banner programs and scripts. In addition a log location needs to be populated. Note: the Private User cannot logon to the host OS where EnterpriseSCHEDULE resides. Also, remember it is the Oracle/Banner namespace that controls access to a Banner functional area not the OS namespace. This can be confusing because sometimes the same user name such as “baninst1” and “banprod” exists in both the Oracle namespace and the host namespaces but they are technically different.

Use of a Default Job and propagation of an OS submit user

Creating a default job by a ESchedule privileged user into a protected folder or analyst’s folder and making the default job readable, allows the OS Submit user to be propagated into any newly created job within that folder. When using a Job template the Submit User does not propagate from the template to the newly created job. This unique create time propagation property of the “default job” allows a user to run Banner objects available without any additional security needs. Access segregate can be retained to its fullest. Note: (a) never use “root” as the User Name in a “default” job and (b) keep ownership of “default job” to the Sys Admin and (c) make “default job” as readable only to Everyone.


Group definitions Access control of users is made easy in ESchedule by the feature groups. Two groups are available by default banadmin and banuser. Banuser is typically used to add read access to Banner folders. Banadmin is typically used to add more access to privileged Banner users. It is common to create additional groups such as banfinaid, banfinance, etc. to allow access to functional folders. To create additional groups you must be a privileged user. Simply right mouse click on /syscontrol/groups and create your new groups. To add and modify access for a group, as a privileged user update the “access” to a folder/job, by adding in the group and its desired access control. As a privilege user to make a private user part of a group right mouse click on a private user’s record in /syscontrol/user and update their group membership to include the group.

Oracle/Banner name space In general as defined by Ellucian, the running of a Banner program or script follows the format similar to: Program {or script} {qualifiers} {Oracle username password} {output

directives}

This true whether you are running from a host console session, Job Submission, or EnterpriseSCHEDULE. It is important to note - it is the {Oracle username password} that controls access to a Banner functional area, not the host OS user. When using Oracle Wallets the same general format is used and the Oracle username password is replace the Oracle Wallet proxy definition. The use of an Oracle Wallet proxy is detected by ESchedule and the JSBANPROXY is paired in use with the Oracle username in place of the Oracle password. Access control of users is made easy in ESchedule by the feature groups. Two groups are available by default banadmin and banuser. Banuser is typically used to add read access to Banner folders. Banadmin is typically used to add more access to privileged Banner users. It is common to create additional groups such as banfinaid, banfinance, etc. to allow access to functional folders. To create additional groups you must be a privileged user. Simply right mouse click on /syscontrol/groups and create your new groups. To add and modify access for a group, as a privileged user update the “access” to a folder/job, by adding in the group and its desired access control. As a privilege user to make a private user part of a group right mouse click on a private user’s record in /syscontrol/user and update their group membership to include the group.


This chapter describes how to: (a) add in your site specific scripting details, (b) how to create your own job includes along with reusable job prototype templates, (c) how to “save/protect from overwrite” your site custom details when upgrading to the next ISE software release. Open an Explorer view within the EnterpriseSCHEDULE Desktop Client by left mouse clicking on the 3rd icon (hovering your mouse over the icon will display “Explorer”). Expand and browse to folder “/default/ban” as they are components of the Banner Schedule module. Take note, jobs starting with “proto_” are your templates (viewable in the explorer by right mouse click “jobfrom”) and by naming convention jobs starting with “bani_” are the set of include pieces that are used to build up the commands within a job.

Custom job command includes There are two predetermined include job definition locations for adding your site specific details if needed, bani_ban_custom_begin and bani_ban_custom_finally. The jobs are not supplied. If you need this functionality simply create the two jobs and add in your details. ISE in future releases will not overwrite these two jobs. Appendix 3 – (13) has an example of a master Banner Job and it shows where these two includes are merged in. When viewing a job’s commands you can click on the “preview” button and see the include pieces merged together along with any preprocessing directives. Schedule does four passes of preprocessing expansion.

Creating additional job prototypes

Many times customers want to modify the ISE job templates and includes. It is recommended you create your own job includes “bani_*” with a naming convention “bani_xyz*” (where xyz is your school’s call letters). Do the same for any template jobs you create such that “proto_*” should become “proto_xyz*”. ISE supports and believes in helping customers create their own templates and includes, however, with future releases ISE reserves the right and has the obligation to improve our templates. This process will many times, overwrite existing ISE jobs and templates. Simply copy and rename your new job pieces. As with many ISE topics, please call or email with questions and Schedule a WebEx overview.

Chapter 6 Creating customs includes with your site’s added details and creating additional job prototypes.


How to make SQL*Plus an option on the “Submit” property page

Many times customers want to add another scripting language and/or add additional scripting choice for generic types of Jobs such as a SQL*plus. ISE provides a flexible option to add any number of additional scripting engine choices in addition to the standard choices of Bash, Ksh, Csh, Expect, Perl etc. You could declare a sqlplus scripting type (maybe a couple of flavors) and then all you have to do is put the sql statements in the job commands. If you edit /schedule_library/sch0_parameter.dat you will see a section as in figure (1) below. Example "CLI_1" below maybe very close to what many schools may need. As a test add the below into your parameter file: CLI_1 = =. /usr/local/admin/settest.shl; sqlplus /nolog

@,sql,0,SQL*Plus

Then restart your Schedule server. On the "submit" property page you

should have a "SQL*Plus" option.

Then create a job trying commands similar to these. (Note: Schedule

should capture the completion status.):

WHENEVER OSERROR EXIT 9;

WHENEVER SQLERROR EXIT SQL.SQLCODE;

connect ((ORAUSER))/((ORAPW))@$TWO_TASK

SET SERVEROUTPUT ON;

EXEC myorakit.gzp_test_proc('static');

exec ((SQL_OWNER)).((SQLOBJECT)) ((SQL_PARMS)):

If this works and you like it, remember certain script pieces that are always the same you can put in an include job. Then make a set of proto type jobs.


Figure 1: !---------------------------------------------------------------------

! Unix/Linux/Windows

! Additional CLIs (command language interpreters) can be specified

that

! will extend the list of known CLIs that are available to use. The

! Schedule WinGUI will augment its list of CLIs based on this

information.

! CLI_n = cli_command, file_extension, pass_parameters,

descriptive_name

! where "_n" is an integer value between 1 and 19. These integers must

! be contigous, i.e. the first missing element ends the list.

! This information is used to compose the command that is issued to

! execute the commands associated with a job. If extra spaces or

! other odd symbols are needed in the cli_command surrond it with

quote

! marks.

!

! By convention, the job's p1-p8 parameters are appended to the

command

! line. Some CLI programs are unable to accept parameters (Ex: OSQL,

MySQL).

! Set pass_parameters to 0 so that p1-p8 are NOT appened to the CLI

command

! line.

! Examples:

! CLI_1 = "cscript ""c:\program files\xmlvbs_engine.wsf"" ",xml,Vbs-

Xml

! CLI_2 = "osql -E -SDBCINT2\SQL2 -dtargetingdw -i",sql,OSql

! CLI_3 = /bin/ksh2000,ksh,ksh2000

! CLI_4 = xperl,xpl,Extended Perl

! CLI_5 = "/oracle_home/bin/sqlplus @",sql,SQL*Plus

! this generates the following commands:

! cscript "c:\program files\xmlvbs_engine.wsf" JOB1_CMDS.xml

! osql -E -SDBCINT2\SQL2 -dtargetingdw -iJOB2_CMDS.sql

! /bin/ksh2000 JOB3_CMDS.ksh

CLI_1 =

! Unix standard CLI extensions

! Run Perl scripts

CLI_20 = perl,pl,1,Perl script

! Run Python scripts


CLI_21 = python,py,1,Python script

! Run expect scripts

CLI_22 = expect,exp,1,Expect script


This chapter describes some commonly used Job Stream (workflow) Concepts: (a) using a job as building block and creating a top down flow with a centralized starting point to control the Job Stream rescheduling, (b) segmenting activity, job tasks, into sequential processing, parallel processing, fanning out, fanning in, when to use initiate dependencies, when to use prerequisite dependencies, (c) propagating global data through the Job Stream (workflow), (d) lastly, expanding the Job Stream (workflow) across the Enterprise (node to node) whereby the Job Stream (workflow) spans host to host (to host …) such as “Linux host1 to Linux host2 and back to Linux host1” and/or “Linux host1 to Windows host2”.

Using a job as building block When viewing jobs along with their property pages many times it’s important to look at jobs as building blocks that can be used to construct a reusable workflow or Job Stream. When you create your first set of jobs many times you’re eager think in terms of what goes into the commands and then running the job. But it’s helpful to think of a job simply as a connection point to other jobs. In fact, jobs in themselves do not require any command definition and many times a job is used as a connection point between other jobs without containing any commands. As an example, the first job in a Job Stream may simple contain the rescheduling definition of the Job Stream. (Note: ISE generally recommends that the head job of the Job Stream contain the Rescheduling definition.) Then further down in a Job Stream, a job may have a resource definition that must be met before the job stream can continue (does a file exist, or has the database been updated etc.) It is also possible to have multiple initiate paths coming from one job whereby if “condition 1” initiate down “path A” if “condition 2” initiate down “path B”. Please refer to the ISE Assistant in the desktop GUI and Install Examples A, B and C to learn more.

Chapter 7 Commonly Used Job Stream (workflow) Concepts.


Managing the flow of your tasks, the Job Stream All Job Streams (workflows) consist of segments of sequential tasks and parallel tasks. Generally speaking the “initiate” job dependency takes care of most Job Stream (workflow) needs. Every downstream initiate “on condition” has a built-in prerequisite that you can define based on a completion status, comparison or expression. The second type of dependency a “prerequisite” is needed when multi up stream jobs need to complete before the downstream job. This occurs when a Job Stream has fanned out into a parallel section and now must contract back into a sequential section.


As with many ISE topics, please call or email with questions and Schedule a WebEx overview.


Propagating global data through the Job Stream The are several ways to propagate data into a job. The most common source for job specific data is through job variable (parameter). For data shared across multiple jobs such as a Job Stream the most common source is a Schedule variable. For Banner jobs ISE has predefined a set of Job variables and prefixed them with the naming convention JV_. Please refer to the “notes” property page of a job if you would like to see the details. Banner specific jobs also share global data starting with a default lookup of values in the /ban_controls folders. Chapter 4 shows several examples of Job Streams and their shared global data that is depicted in the various layouts.

Managing the Job Stream across the Enterprise and multiple hosts Job Streams (workflows) can span across your Enterprise of host machines wherever

EnterpriseSCHEDULE servers are installed. Various platforms are supported by ISE. A Job Stream can

span from Linux to Windows, Linux to UNIX to Windows and beyond.


Appendix A Installating EnterpriseSCHEDULE to automate Banner

Installation Procedures – which includes Schedule server, Schedule desktop client, Schedule IIS Host, Schedule Sql stored procedure, and Schedule Automate Banner import module. 1) Install the ISE EnterpriseSCHEDULE Server which will automate and manage the Banner

Job Submission library of executables and Scripts. Note: this installation should reside on

the same host as the Job Submission library ($BANNER_LINKS and $EXE_HOME). The

Banner database location may or may not reside on the same host.

Typically, this is a Linux or UNIX environment. Refer to document “EnterpriseSCHEDULE

Release Notes for HP-UX, Solaris, AIX and Linux” for the latest ISE Schedule server

installation instructions. This installation task requires root access. The Unix/Linux Install Kit

file readme.txt will also have the installation instruction which is typically a binary ftp

download of a file named something like schedule77xx.rpm.gz followed by commands

something like:

gunzip schedule77xx.rpm.gz

rpm --install schedule77xx.rpm

2) Install the ISE EnterpriseSCHEDULE desktop client for Windows on one or more

desktops. Refer to document “EnterpriseSCHEDULE Release Notes for Windows” for the

latest client installation instructions. The desktop client allows users the ability to manage

and monitor the Scheduling of Banner applications. This installation task requires

administrator access. The Windows install Kit file readme.txt will also have the installation

which is typically a binary ftp download of something like ISESchClient77xx.exe and then

double click on ISESchClient77xx.exe.

3) Review document “Using the EnterpriseSCHEDULE License Manager” as version 7.7

of the License Manager has added functionality to enable management of your licenses

across the various Server and Desktop hosts from a single management point.


Note: Once the EnterpriseSCHEDULE desktop client is installed there will also be

documentation available in the EnterpriseSCHEDULE folder.


4) Install the ISE EnterpriseSCHEDULE IIS Host for Windows on a designated Windows

host using ISEBanWebxxx.exe. This installation task requires Administrator access.

Additional general ISE IIS information can be obtained in document “EnterpriseSCHEDULE

Web Client”. The Windows install Kit file readme.txt will also have the latest installation

instructions. After downloading the installation executable double click on the

EnterpriseSCHEDULE executable and choose Custom Install during installation and check

off Web Client web site in the list of Features. Click Next to continue and complete the

Installation. This procedure will also install Internet Information Services (IIS) on the server.

5) Import and install the ISE Stored Procedure Package (ISEBanSqlxxx.sql) onto the

Oracle database such as as executable by all. At a job’s runtime, this utility loads the

Banner gjbprun table with the job’s provided parameter save set along with any runtime

parameters and returns a unique one up number to be run with a given instance of the job.

This installation task requires dba access.

Note: The stored procedure must be global


6) Import the ISE Automate Banner job templates - This requires root or privileged access.

Copy file ISEBandefxxx.schedule to a folder such as C:\tmp and onto a desktop Windows

machine where the EnterpriseSCHEDULE client is installed. From the Explorer View in

EnterpriseSCHEDULE select “FileImport” and browse to and select the import file

ISEBandefxxx.schedule. Importing this file using the Schedule desktop client as a

privileged user will create a sub folder /default/ban where the ISE Banner Job templates

reside.

Alternate method: After copying the file to the C:\tmp directory issue the command

C:\> schedule source ISEBandefxxx.schedule

This will perform the same procedure as the Import procedure described above.

Note: If ISEBandefxxx.schedule (or any *.schedule import file) is not imported with the

correct privilege such as “change user access”, you may see errors such as “identifier not

found”.

7) Run the setup job (setup_ban_controls_folder) – This job creates the default folder

/ban_controls that contains many of the Banner configuration variables. This task requires

root or privileged access. From a Schedule desktop client session, “submit” job

“/default/ban/setup_ban_controls_folder” by opening an explorer session, expanding the

folder “/default/ban” and right mouse clicking on job

“/default/ban/setup_ban_controls_folder” and selecting “Start Now …”.


Note: after the initial installation many of these same variables can be duplicated in multiple

places in any parent and/or child folder throughout the life cycle of creating jobs and job

streams such that /ban_controls is the fall back default set of control variables. Then for a

given control variable such as Bansid, {database ID}, there is a 3 level path look up of

a) “current folder”,

b) “parent folder” and

c) “/Ban_control {default folder}”.

This gives each variable a 3 level control of options whereby variable such as /Ban_controls/Bansid could be “PROD” for most jobs and then the variable in folder /My_test_jobs/Bansid could be TEST allowing you access to two different databases in an organized fashion. Command alternative: C:\> schedule submit setup_ban_controls_folder


8) Configure the base set of Banner and Oracle controls - This task requires root or

privileged access.

From a Schedule desktop client session open an explorer session, expanding the folder

“/default/ban” and right mouse clicking on job “/default/ban/setup_ban_controls_folder” and

select “Properties …”.

Populate the options page of job “/default/ban/setup_runtime_ban_oracle_defaults”.


Then submit job“/default/ban/setup_runtime_ban_oracle_defaults” by right mouse clicking

on job “/default/ban/setup_ban_controls_folder” and selecting “Start Now …”.

9) Importing ISEBandemo.schedule requires the job

“/default/ban/setup_ban_controls_folder” to be submitted first. Also, if OS user “baninst1” is

not present globally change the text file ISEBandemo.schedule to an appropriate defined

OS user. The typically error in this case is “identifier nnnn”


Appendix B Banner Automation Folder and Job Template overview.

Viewpoints for the individual interested in the scripting details 1) It’s important to understand and possible review some key points of the ISE

EnterpriseSCHEDULE’s capabilities as a programming aid, highlighted in documents as

such “EnterpriseSCHEDULE Preprocessing” and “Using Job Prototypes in

EnterpriseSCHEDULE”. The EnterpriseSCHEDULE Banner job templates leverage many of

the built-in Schedule tool kit features. The definition of each Banner job template starts with

a master include scripting piece that in turn is a make-up of a set of include scripting pieces.

The pieces will have global and job variable definitions that are expanded, evaluated, and

executed at run time. Many of the pieces are the same across all of the templates and are

adjustable building blocks. Such that the layers of scripting pieces allow flexibility, reusability

and ease of use to the end user. Frequently, end users enhance existing Banner Job

templates and create their custom Job templates. Yet at the same time, it is possible to run

the entire Banner installed library of executables and scripts with initial set of ISE Banner

Job templates.

2) Typical Steps within a Banner job a template.

a) Every template allows for the Banner job, Oracle user, Parameter save set and optional

runtime values.

b) The Banner environment is setup first by using the master values from the folder

/ban_controls and these values can be locally adjusted and overridden in the local

and/or parent folder of a job.

c) The parameter save set of values and any defined runtime values are loaded into the

gjbprun for the instance of the job run.

d) The Banner installed program or script is run.

e) Values within Banner output log and/or list file can be searched for exceptions that when

found cause a job failure. The ISE’s job has a log file whereby the Banner output log file

is “echo’d” into for ease of viewing.

f) Within the same Job, a built-in optional move of output files can be invoked through a

selection of choices of ranging from copy, ftp, email attached and Banner’s Gurinso

utility. In addition, a downstream job can be created that has the runtime details of the

output files. This allows for custom scripting for Schools that have data movement needs

that are beyond the basic built-in options.

g) See an example job template /default/ban/bani_cobol_job in Appendix 3 - Example job

template /default/ban/bani_cobol_job.

h) Banner Job variables are listed in the “notes” property page with descriptions while

current values are displayed in the “options” property page.


Example job template

3) Break down of a template.


4) Prototype definitions such as /default/ban/proto_cobol_template_job includes the master

include such as /default/ban/bani_cobol_job and it allows for the easy creation of similar

jobs with a simple right mouse click “New Job from Ban ”


5) Once a job is created from a Prototype definition such as

/default/ban/proto_cobol_template_job and the job specific details are filled in such as the

Banner program name, the runtime expansion of the includes and variable substitution can

be viewed by clicking “preview” on the job’s “Commands” property page before running the

job.

echo -e

"\n**********************************************************************************"

echo -e "*** ISE Job Execution using master template /default/ban/Bani_cobol_job"

echo -e

"**********************************************************************************\n"

date

echo -e

"\n**********************************************************************************"

echo -e "*** Loading Banner environment"

echo -e

"**********************************************************************************\n"

# Streampath

Streampath="/u01/banjobs/gurjobs/PRODN/"


# Streamfname

Streamfname="Daily_banner_jobs_"

# Thisday

Thisday="20170112"

if [[ -z "$Streampath" || -z "$Streamfname" ]]; then

SummPath=""

else

SummPath=$Streampath$Streamfname$Thisday".log"

fi

# Update stream summary path -- JV_STREAM_SUMMARY_PATH allows last run view

schedule ch /ban_demo/cobol_job -proc:variable="(JV_STREAM_SUMMARY_PATH=\"$SummPath\")" -log

# HOME is carried down into the Banner environment

HOME=/banner/ise/dataload/restran/glbdata_1831335.*

export HOME

# Set ORACLE environment

export ORACLE_SID="PROD"

export ORAENV_ASK="NO"

#. /usr/local/bin/oraenv

# Additional site specific setup script

echo "Other/Global Variables for Banner runtime have been loaded as follows:"

echo "Banner Output Home = "/banner/ise/dataload/restran/glbdata_1831335.*

echo "Banner Oracle User = "baninst1

echo "Password = ********"

echo "Sid = "PROD

echo "Print = "DATABASE

echo "Stream Summary Path = "$SummPath

echo -e

"\n**********************************************************************************"

echo -e "*** Loading Banner Job variables"

echo -e

"**********************************************************************************\n"

if [[ "glbdata" == '' ]]; then

echo "Banner Program field is blank exiting."

exit 8

fi

if [[ "baninst1" == '' ]]; then

echo "Parameter Set User is blank exiting."

exit 8

fi

if [[ "TRACKING_GROUPS" == '' ]]; then

echo "Parameter Set Name is blank exiting."

exit 8

fi

override1=""88,1516,Aidy""

export override1

override2=""

export override2

override3=""

export override3

override4=""

export override4


override5=""

export override5

echo -e

"\n**********************************************************************************"

echo -e "*** BANNER JOB PARAMETER SET\n"

echo -e "*** Banner Program = glbdata"

echo -e "*** Param Set User = baninst1"

echo -e "*** Param Set Name = TRACKING_GROUPS"

echo -e

"**********************************************************************************\n"

#

# Optional begin action site customized scripting, USE -)) BELOW

#

#echo -e

"\n**********************************************************************************"

#echo -e "*** Executing Gjob_params script\n"

#echo -e

"**********************************************************************************\n"

#

# Interface to Stored Procedure ISE_BANNER.gjobs_parms

#

#-- Overloaded callable subprograms, takes different number of arguments

#

# PROCEDURE gjob_parms (job_name VARCHAR2, user_id VARCHAR2, param_set VARCHAR2, debug_flag

VARCHAR2);

#

# PROCEDURE gjob_parms (job_name VARCHAR2, user_id VARCHAR2, param_set VARCHAR2,

# aidyear VARCHAR2, termcode VARCHAR2, date_param VARCHAR2,

# override1 VARCHAR2, override2 VARCHAR2, override3 VARCHAR2,

# override4 VARCHAR2, override5 VARCHAR2, debug_flag VARCHAR2);

#

# Uncomment the next two lines for debugging of gjob_parms

#debug_flag="Y"

#export debug_flag

#

# To use any of the dynamic parameters you may need to modify the commands within your jobs.

#

# make an upper case version of certain vars for use as db query parameters

UP_USER=ècho ((JV_PARM_SET_USER)) | tr "[a-z]" "[A-Z]"`

UP_JOB=ècho glbdata | tr "[a-z]" "[A-Z]"`

UP_PARAM_SET=ècho ((JV_PARM_SET_NAME)) | tr "[a-z]" "[A-Z]"`

# get a temp file name to spool into

tempFileName=`mktemp`

echo -e "\ntempFileName=$tempFileName"

echo -e "\Saving Parameter Values to GJBPRUN...\n"

if [ -n "$date_param" ] || [ -n "$override1" ]; then

echo "check all possible dynamic variables"

# create a new one up number and store to a file

# NOTE that some of the parameters are upper case!

sqlplus baninst1/pjiinst << STOP

set serveroutput on;

set time off;


set feedback;

spool $tempFileName

execute

ise_banner.gjob_parms('$UP_JOB','$UP_USER','$UP_PARAM_SET','$aidyear','$termcode','$date_para

m','$override1','$override2','$override3','$override4','$override5','$debug_flag');

spool off;

exit;

STOP

else

# If termcode is defined then we need to pass it to banner

# assumes aidyear is defined in this case

#

if [ -n "$termcode" ]; then

echo "termcode $termcode is defined aidyear $aidyear"





set time off;

set feedback;

spool $tempFileName

execute

ise_banner.gjob_parms('$UP_JOB','$UP_USER','$UP_PARAM_SET','$aidyear','$termcode',null,null,n

ull,null,null,null,'$debug_flag');

spool off;

exit;

STOP

else

# If aidyear is defined then we need to pass it to banner

#

if [ -n "$aidyear" ]; then

echo "aidyear $aidyear is defined"





set time off;

set feedback;

spool $tempFileName

execute

ise_banner.gjob_parms('$UP_JOB','$UP_USER','$UP_PARAM_SET','$aidyear',null,null,null,null,nul

l,null,null,'$debug_flag');

spool off;

exit;

STOP

else

# No additional runtime parameters defined to pass to banner

#

echo "No additional runtime (dynamic) parameters defined"






set time off;

set feedback;

spool $tempFileName

execute ise_banner.gjob_parms('$UP_JOB','$UP_USER','$UP_PARAM_SET','$debug_flag');

spool off;

exit;

STOP

fi

fi

fi

# get one up number from file and store to system variable

one_up=`grep ^[0-9] $tempFileName | sed 's/ *$//'`

echo $one_up > $tempFileName

echo -e "\Saved Parameter Values to GJBPRUN, one_up=$one_up \n"

#

echo "Cobol Pref = $COBPREF"

#

echo -e

"\n**********************************************************************************"

echo -e "*** Executing Cobol Job\n"

echo -e "*** Job parameter JV_PROGRAM controls this process, glbdata "

echo -e

"**********************************************************************************\n"

if [ -z "$one_up" ]; then

echo -e "\none_up NOT found, you need gjob_parms to finish successfully before this

program can execute.\n"

exit 8

else

#

# Build up output file names

#

IFILE="glbdata_"$one_up

echo -e "\nJob glbdata the One Up Number is = $one_up"

echo -e "\nIFILE=$IFILE"

echo -e "\n"

IPATHFILELIS=/banner/ise/dataload/restran/glbdata_1831335.*"/"$IFILE".lis"

IPATHFILELOG=/banner/ise/dataload/restran/glbdata_1831335.*"/"$IFILE".log"

IPATHFILECVS=/banner/ise/dataload/restran/glbdata_1831335.*"/"$IFILE".cvs"

IPATHFILEALL=/banner/ise/dataload/restran/glbdata_1831335.*"/"$IFILE".*"

#

# Update runtime JV_RUNTIME_OUTPUT_FILENAME

#

IPATHFILE=/banner/ise/dataload/restran/glbdata_1831335.*"/"$IFILE

schedule ch /ban_demo/cobol_job -proc=var="(JV_RUNTIME_OUTPUT_FILENAME=\"$IPATHFILE\")" -log

#

# Execute

#

# Phew! now we can actually launch the banner job!

# NOTE: that the 4th parameter (Job/Program) is upper case!

# while invoking the shl script (Job/Program) is lower case.

#

$BANNER_LINKS/glbdata.shl baninst1 pjiinst $one_up $UP_JOB DATABASE

sts=$?


if [ $sts != 0 ]

then

echo "Job glbdata FAILED with error $sts"

exit $sts

fi

# Cleaup by removing temp file

#

# rm $tempFileName

#

# Make this job's One_up number available to any initiated downstream job(s) through set_tag

#

schedule chque -entry=$SCHEDULE_ENTRY -set_tag="'$IFILE'" -log

echo "schedule chque -entry=$SCHEDULE_ENTRY -set_tag=$IFILE -log"

echo -e "Banner LIS file should be "$IPATHFILELIS"\n"

if [ -r $IPATHFILELIS ] ; then

#echo "Banner lis file exists..."

else

echo "No Banner lis file exists..."

fi

echo -e "\n"

echo "Banner LOG file should be "$IPATHFILELOG

if [ -r $IPATHFILELOG ] ; then

echo "Banner log file exists...here it is:"

echo -e "\n***---***---***---***---***---***---***---***---***---***---***---***---***---***-

--***---***---***\n"

echo -n

cat $IPATHFILELOG

echo -e "\n***---***---***---***---***---***---***---***---***---***---***---***---***---***-

--***---***---***\n"

else

echo "No Banner log file exists..."

fi

echo -e

"\n**********************************************************************************"

echo -e "*** Moving data section\n"

echo -e

"**********************************************************************************\n"

write_to_db=`echo | tr "[A-Z]" "[a-z]"`

action=`echo Send as E-mail attachment | tr "[A-Z]" "[a-z]"`

#

# GURINSO

#

if [[ "$write_to_db" == 'true' ]]; then

echo -e

"\n**********************************************************************************"

echo -e "*** GURINSO\n"

echo -e

"**********************************************************************************\n"

echo "$EXE_HOME/gurinso -n $one_up -l $IPATHFILEALL -j glbdata -w baninst1 baninst1/pjiinst"

$EXE_HOME/gurinso -n $one_up -l $IPATHFILEALL -j $JOB -w baninst1 baninst1/pjiinst

fi

fi


#

# Email

#

if [[ "$action" == 'email' ]]; then

echo -e

"\n**********************************************************************************"

echo -e "*** Banner Job files sent as Attachment(s) in completed email \n"

echo -e

"**********************************************************************************\n"

format=`echo .* | tr "[A-Z]" "[a-z]"`

if [[ "$format" == 'all' ]]; then

email_attachment=/banner/ise/dataload/restran/glbdata_1831335.*'.*'

else

email_attachment=/banner/ise/dataload/restran/glbdata_1831335.*'.'.*

fi

else

email_attachment=""

fi

schedule ch /ban_demo/cobol_job -proc=var="(JV_EMAIL_ATTACHMENT=\"$email_attachment\")" -log

#

# Copy

#

if [[ "$action" == 'copy' ]]; then

echo -e

"\n**********************************************************************************"

echo -e "*** Banner Job files sent through Copy \n"

echo -e

"**********************************************************************************\n"

if [[ ".*" == 'all' ]]; then

cp /banner/ise/dataload/restran/glbdata_1831335.*.* /tmp

else

cp /banner/ise/dataload/restran/glbdata_1831335.*..* /tmp

fi

sts=$?

if [ $sts = 0 ]

then

echo "COPY of Banner files succeeded."

else

echo "COPY of Banner files FAILED!"

fi

fi

#

# Ftp

#

if [[ "$action" == 'ftp' ]]; then

echo -e

"\n**********************************************************************************"

echo -e "*** Banner Job files sent through Ftp \n"

echo -e

"**********************************************************************************\n"

if [[ ".*" == 'all' ]]; then

ftp -n -i -v orion <<EOF

user pjones pjiinst

ascii

put /banner/ise/dataload/restran/glbdata_1831335.*.* /tmp

quit


EOF

else

ftp -n -i -v orion <<EOF

user pjones pjiinst

ascii

put /banner/ise/dataload/restran/glbdata_1831335.*..* /tmp

quit

EOF

fi

sts=$?

if [ $sts = 0 ]

then

echo "FTP COPY of Banner files succeeded."

else

echo "FTP COPY of Banner files FAILED!"

fi

fi

#

# Add entry to stream summary file

#

if [[ "/banner/ise/dataload/restran/Dail_banner_jobs_01112016.log" != '' ]]; then

#

#

echo -e

"\n**********************************************************************************"

echo -e "*** STREAM SUMMARY FILE\n"

echo -e

"**********************************************************************************\n"

#

echo `date`" Program glbdata ParameterSetUser baninst1 ParameterSetName TRACKING_GROUPS " >>

$SummPath

fi

fi

#

# SCRAPE log and lis files

#

scrape_status=0

if [[ "JV_SCRAPE_LOGFILE" == 'true' ]]; then

. /schedule_library/scrapelog.bash incl_job=/ban_controls/bani_scrapelog_keys

scrape_status=$?

fi

if [[ "JV_SCRAPE_LOGFILE" == 'true' && $scrape_status -eq 0 ]]; then

. /schedule_library/scrapelog.bash incl_job=/ban_controls/bani_scrapelis_keys

file=$IPATHFILELIS

scrape_status=$?

fi

#

# Optional end action site customized scripting

#

#

echo -e

"\n**********************************************************************************"

echo -e "*** ISE JOB DONE"

echo -e

"**********************************************************************************\n"


if [[ $scrape_status -ne 0 ]]; then

exit $scrape_status

fi

6) An example master template “/default/ban/bani_cobol_job” that is a

makeup of other small include pieces. Note: this is what drives the

expanded scripting listed in the “preview” listing above.

((comment*))

#

# SCHEDULE V7.6 15-JAN-2016

# ISE Inc.

# Copyright (c) 2016

#

# For additional print lines move "set debug_prnt" line command below "endcomment" line.

((set debug_prnt "Y"))

#

((endcomment*))

echo -e

"\n**********************************************************************************"

echo -e "*** ISE Job Execution using master template ((JV_BANI_JOB_ACTION))"

echo -e

"**********************************************************************************\n"

date

echo -e

"\n**********************************************************************************"

echo -e "*** Loading Banner environment"

echo -e

"**********************************************************************************\n"

((include /default/Ban/bani_ban_env))

echo -e

"\n**********************************************************************************"

echo -e "*** Loading Banner Job variables"

echo -e

"**********************************************************************************\n"

((include /default/Ban/bani_job_vars))

#

# Optional begin action site customized scripting, USE -)) BELOW

#

((include /default/Ban/bani_ban_custom_begin -))

#echo -e

"\n**********************************************************************************"

#echo -e "*** Executing Gjob_params script\n"

#echo -e

"**********************************************************************************\n"

((include /default/Ban/bani_ise_gjob_params))

#


echo "Cobol Pref = $COBPREF"

#

echo -e

"\n**********************************************************************************"

echo -e "*** Executing Cobol Job\n"

echo -e "*** Job parameter JV_PROGRAM controls this process, ((JV_PROGRAM)) "

echo -e

"**********************************************************************************\n"

if [ -z "$one_up" ]; then

echo -e "\none_up NOT found, you need gjob_parms to finish successfully before this

program can execute.\n"

exit 8

else

#

# Build up output file names

#

IFILE="((JV_PROGRAM))_"$one_up

((include /default/Ban/bani_ban_output_files))

#

# Execute

#

# Phew! now we can actually launch the banner job!

# NOTE: that the 4th parameter (Job/Program) is upper case!

# while invoking the shl script (Job/Program) is lower case.

#

((if_not_blank debug_prnt*))

echo -e "Banner links is = "$BANNER_LINKS"\n"

echo -e "\n"

echo "$BANNER_LINKS/((JV_PROGRAM)).shl ((JV_BANNER_RUN_USER)) ((JV_BANNER_RUN_PSWD))

$one_up $UP_JOB ((JV_BANNER_PRINT))"

((endif*))

$BANNER_LINKS/((JV_PROGRAM)).shl ((JV_BANNER_RUN_USER)) ((JV_BANNER_RUN_PSWD)) $one_up

$UP_JOB ((JV_BANNER_PRINT))

((include /default/Ban/bani_check_job_status))

# Cleaup by removing temp file

#

# rm $tempFileName

#

# Make this job's One_up number available to any initiated downstream job(s) through

set_tag

#

((include /default/Ban/bani_ifile_copied_to_streams_settag))

echo -e "Banner LIS file should be "$IPATHFILELIS"\n"

if [ -r $IPATHFILELIS ] ; then

#echo "Banner lis file exists..."

else

echo "No Banner lis file exists..."

fi

echo -e "\n"

echo "Banner LOG file should be "$IPATHFILELOG

if [ -r $IPATHFILELOG ] ; then

echo "Banner log file exists...here it is:"

echo -e "\n***---***---***---***---***---***---***---***---***---***---***---***---***---

***---***---***---***\n"

echo -n


cat $IPATHFILELOG

echo -e "\n***---***---***---***---***---***---***---***---***---***---***---***---***---

***---***---***---***\n"

else

echo "No Banner log file exists..."

fi

echo -e

"\n**********************************************************************************"

echo -e "*** Moving data section\n"

echo -e

"**********************************************************************************\n"

write_to_db=`echo ((JV_GJIREVO_WRITE_TO_DB)) | tr "[A-Z]" "[a-z]"`

action=`echo ((JV_SELECT_ACTION)) | tr "[A-Z]" "[a-z]"`

#

# GURINSO

#

if [[ "$write_to_db" == 'true' ]]; then

((include /default/Ban/bani_gurinso))

fi

#

# Email

#

((include /default/Ban/bani_email))

#

# Copy

#

if [[ "$action" == 'copy' ]]; then

((include /default/Ban/bani_copy))

fi

#

# Ftp

#

if [[ "$action" == 'ftp' ]]; then

((include /default/Ban/bani_ftp))

fi

#

# Add entry to stream summary file

#

if [[ "((JV_STREAM_SUMMARY_PATH))" != '' ]]; then

((include /default/Ban/bani_summary))

fi

fi

#

# SCRAPE log and lis files

#

((include /default/ban/bani_scrape))

#

# Optional end action site customized scripting

#

((include /default/Ban/bani_ban_custom_finally -))

#


echo -e

"\n**********************************************************************************"

echo -e "*** ISE JOB DONE"

echo -e

"**********************************************************************************\n"

if [[ $scrape_status -ne 0 ]]; then

exit $scrape_status

fi

enterpriseschedule getting started with...

Documents