BATCH ----------------------- BATCH OPTIONS MENU ----------------------------
OPTION ===> 3
1 BUILD SCL - Build batch SCL actions
2 EDIT - Edit request data set
3 SUBMIT - Submit job for batch processing
4 VALIDATE - Check request data set for syntax errors
5 BUILD JCL - Enter additional JCL to be included with the job
REQUEST DATA SET:
PROJECT ===> OTLD94 APPEND ===> N (Y/N)
GROUP ===> ENDEVOR INCLUDE JCL ===> N (Y/N)
TYPE ===> SCL
MEMBER ===> PGMADD
OTHER PARTITIONED OR SEQUENTIAL DATA SET:
DSNAME ===>
JOB STATEMENT INFORMATION:
===> //OTXX94# JOB (44001,FS01,00000,1111),'PROJECT C583', => PROJECT NAME
===> // CLASS=A,MSGCLASS=H,NOTIFY=OT???? => YOUR ID
===> //*
===> //*$AVRS C=OTCACTSD =>(comment what program/linkcard/binddeck/sysin)
NOTE: Make sure the project code in the jobcard is correct. Use Class = A if there are many elements involved.
----------------------------------------------------------------------------------
Select Option 3 to submit the job. This job:
(a) creates a compiled listing;
(b) creates a load module in the appropriate stage U load library or object code in the appropriate stage U object library;
(c) for DB2 programs, creates the DBRM member in the appropriate stage U dbrm library.
• When done, submit the job using jobname OTXX94# & msgclass H (SDSF).
6. Check Stage U libraries for your updated module (can’t move to Stage C if your
not in Stage U). See library document for library dataset names.
7. MOVE - From Stage U to Stage C (Test).
After a successful add, update or generate (for type LINKCARD) to Stage U, a MOVE is done from STAGE U to STAGE C.
You should do all your MOVES in one package (after the ADDS, UPDATES or GENERATES have executed successfully), however, when the package executes, the MOVES will not necessarily be executed in the order that you built the SCL.
The objective of the mapped environment is to use one package for the entire process so this package should contain all elements needed for production. Remember the package name for implementation purposes.
The current ELEMENT TYPE Sequence Processing order for processing packages is available for viewing (listed below) or by going to ENDEVOR panel E;4;1;7 (DISPLAY TYPE). In the ENVIRONMENT ===> field enter 'CLAIMST', leave the SYSTEM ===> field blank, and the TYPE ===> field blank, select the STAGE ===> you wish to view
ORDER OF OPERATIONS:
--------------------------- TYPE SELECTION LIST ------------ Row 1 to 9 of 9
COMMAND ===> SCROLL ===> CSR
CURRENT ENV: CLAIMST STAGE ID: U SYSTEM: ACES
NEXT ENV: CLAIMST STAGE ID: C SYSTEM: ACES
TYPE TYPE DESCRIPTION
MFS ACES MFS
BINDDECK ACES LINK BIND CONTROL STATEMENTS
LINKCARD ACES LINK CONTROL STATEMENTS
COPYBOOK ACES COPYBOOKS
PROC ACES JCL PROCEDURES
UTL ACES CONTROL CARDS/JOBSYSIN
ASSM ACES ASSEMBLER PROGRAMS
COBOL ACES COBOL PROGRAMS
TELON ACES TELON PROGRAMS
******************************* Bottom of data ********************************
