ADD the program into Stage U through the BATCH option.
E - ENDEVOR or 3.PP.E
4 - CLAIMST
3 - BATCH
1 - BUILD SCL (Example Follows)
2 - ADD/UPDATE (Example Follows)
3 - Submit SCL (Example Follows)
Option 1 - BUILD SCL (Example below).
BATCH ----------------------- BATCH OPTIONS MENU ----------------------------
OPTION ===> 1
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 ===> Your Library APPEND ===> N (Y/N)
GROUP ===> ENDEVOR INCLUDE JCL ===> N (Y/N)
TYPE ===> SCL
MEMBER ===> PGMADD
OTHER PARTITIONED OR SEQUENTIAL DATA SET:
DSNAME ===>
EXAMPLE OF THE JOB STATEMENT INFORMATION ON THE NEXT PAGE…
JOB STATEMENT INFORMATION:
JOB STATEMENT INFORMATION:
===> //OTXX94# JOB (44001,FS01,00000,1111),'PROJECT C583', => PROJECT NAME
===> // CLASS=A,MSGCLASS=J,NOTIFY=OT???? => YOUR ID
===> //*
===> //*$AVRS C=OTCACTSD =>(comment what program/linkcard/binddeck/sysin)
OPTION 2 - ADD/UPDATE (Example below).
------------------------------- SCL GENERATION ---------- 0 REQUEST(S) BUILT
OPTION ===> 2
1 DISPLAY - Display an element
2 ADD/UPDATE - Add or update an element into stage U
3 RETRIEVE - Retrieve or copy an element
4 GENERATE - Execute the Generate Processor for this element
5 MOVE - Move an element to the next inventory location
6 DELETE - Delete an element
7 PRINT ELEMENT - Print elements, changes and detail change history
8 SIGNIN - Explicitly sign-in an element
9 TRANSFER - Transfer elements between two ENDEVOR locations
10 PRINT MEMBER - Print a compressed listing or member
11 LIST ELEMENT - Create List actions for ENDEVOR elements
12 LIST MEMBER - Create List actions for external members
13 ARCHIVE - Archive elements
REQUEST DATA SET: OTXX94.LIB.CNTL(TEMP)
APPEND: N
OPTION 2 - ADD/UPDATE (Example Continued).
---------------------------- ADD/UPDATE ELEMENTS ----------------------------
OPTION ===> a
blank - Member list A - Add an element U - Update an element
TO ENDEVOR: ACTION OPTIONS:
ENVIRONMENT ===> CLAIMST CCID ===>
SYSTEM ===> ACES GENERATE ELEMENT ===> Y (Y/N)
SUBSYSTEM ===> ACES DELETE INPUT SOURCE ===> N (Y/N)
ELEMENT ===> othirpt1 NEW VERSION ===>
TYPE ===> COBOL OVERRIDE SIGNOUT ===> N (Y/N)
STAGE: U PROCESSOR GROUP ===>
COMMENT ===> brief explaination UPDATE IF PRESENT ===> N (Y/N)
of change
FROM ISPF LIBRARY: LIST OPTIONS:
PROJECT ===> OTXX94 DISPLAY LIST ===> Y (Y/N)
LIBRARY ===> END
TYPE ===> SOURCE
MEMBER ===> othirpt1 THRU MEMBER ===>
FROM OTHER PARTITIONED OR SEQUENTIAL DATA SET:
DATA SET NAME ===>
After you have typed in all the information needed on the ADD/UPDATE screen,
PF3 to the SCL GENERATION screen. Note that in the upper right hand corner of this
screen a message reads "1 REQUEST(S) BUILT". This message verifies that the ADD/UPDATE of the element was built into the SCL data set and is ready to
submit as a batch job.
From the SCL GENERATION screen, PF3 to the BATCH OPTIONS MENU screen.
Processor Group Notes :
If the program existed in Endevor, a Processor Group has been assigned. Leave the PROCESSOR GROUP (under ACTION OPTIONS) blank, as in the above example. Endevor uses the existing Processor Group.
If you are adding DB2 to an existing program or adding a program for the first time - a NEW Processor Group needs to be assigned to the program. To assign a Processor Group, on the ADD/UPDATE ELEMENTS screen: type one of the existing processor groups in, or place "*" on the PROCESSOR GROUP option. When you type an asterisk, Endevor displays the entire list of Processors for the type indicated (COBOL, TELON, PL1 or ASSM). Place an "S" next to the appropriate processor and hit enter. The following shows an example of the display for processor group selection.
Viewing a List of Processor Groups:
E - ENDEVOR/MVS Environment Selection
4 - CLAIMST
1 - DISPLAY
8 - PROCESSOR GROUP
Fill out the Environment, System, Type, and Stage. Put a * in the Group…
The available choices to date are:
ACES: Stage U
--------------------- PROCESSOR GROUP SELECTION LIST ------- Row 1 to 5 of 5
COMMAND ===> SCROLL ===> CSR
CURRENT ENV: CLAIMST STAGE ID: U SYSTEM: ACES TYPE: TELON
NEXT ENV: CLAIMST STAGE ID: C SYSTEM: ACES TYPE: TELON
PROCESSOR
GROUP PROCESSOR GROUP DESCRIPTION
*NOPROC* DEFAULT PROCESSOR -- NO COMPILE
CMVNIL47 ONLINE TELON 2.4 COB/MVS TABLE SYSTEM LOAD LIBRARY
CMVNIODD ONLINE TELON 2.4 COB/MVS STATIC OBJECT DRIVER PGMS (Telon Drivers)
CMVNIODS ONLINE TELON 2.4 COB/MVS STATIC OBJECT SUB PROGRAM (Telon subprograms
w/DB2)
CMV2IODS ONLINE TELON 2.4 COB/MVS DB2 STATIC OBJ SUB PROGRM (Telon subprograms
w/out DB2)
******************************* Bottom of data ********************************
LEB2IL47 ONLINE TELON 2.4 COB/MVS LINK WITH DB2
LEBNIL47 ONLINE TELON 2.4 COB/MVS LINK WITHOUT DB2
ACES: Stage C
--------------------- PROCESSOR GROUP SELECTION LIST ------- Row 1 to 4 of 4
COMMAND ===> SCROLL ===> CSR
CURRENT ENV: CLAIMST STAGE ID: C SYSTEM: ACES TYPE: TELON
NEXT ENV: CLAIMS STAGE ID: 2 SYSTEM: ACES TYPE: TELON
PROCESSOR
GROUP PROCESSOR GROUP DESCRIPTION
*NOPROC* DEFAULT PROCESSOR -- NO COMPILE
CMVNIODD ONLINE TELON 2.4 COB/MVS STATIC OBJECT DRIVER PGMS (Telon Drivers)
CMVNIODS ONLINE TELON 2.4 COB/MVS STATIC OBJECT SUB PROGRAM (Telon subprograms
w/DB2)
CMV2IODS ONLINE TELON 2.4 COB/MVS DB2 STATIC OBJ SUB PROGRM (Telon subprograms
w/out DB2)
******************************* Bottom of data ********************************
LEB2IL47 ONLINE TELON 2.4 COB/MVS LINK WITH DB2
LEBNIL47 ONLINE TELON 2.4 COB/MVS LINK WITHOUT DB2
ALF:
COBOL Stage 1:
CIINBL48 - COBOLII BATCH PROCESSOR AMODE31
CIINBOD8 - COBOLII OBJECT MODULES
CII2BL48 - COBOLII DB2 BATCH PROCESSOR AMODE31
TELON Stage 1:
CIA2BOD8 COBOLII/DB2 TELON 2.4 SUB PROGRAM OBJECT MODULE
CIENBOD8 COBII TELON 2.4 BASE SUB PROGRAM OBJECT MODULE
CIFNBOD8 COBII TELON 2.4 BASE DRIVER PROGRAM OBJECT MODULE
COBNBLB0 COBOLII TELON 2.4 BATCH PROCESSOR AMODE31
If a new program has been created that does not fit into one of these groups, then a NEW Processor Group will have to be defined.
OPTION 3 - Submit SCL (Example below).
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.
No comments:
Post a Comment