$$
We need tp prepare aan ADDSCL to compile a program through Endeavor.The following points to be noted while preparing ADDSCL.
1.In which environment are we going to add a program.?As you all know there are different environments in Endeavor such as Production, Test, Accpetance, QuickFix Etc., and it is installation dependent.
2.Select the environment, say if you are adding a program in Test environment
3.Goto Test environment => Choose option Batch => Build SCL => ADD/Update SCL => here we need to give CCID, Processor Group, Override signout(Y/N), Replace Member(Y/N), Element, Type, Comments Etc.,
And finally from which PDS we are adding an element.
4. PF3(2 times) --> leads to the Batch main screen
5. choose Option 2 in Batch main menu i.e., EDIT
6.Check the ADDSCL whether everything is correct.
7. Choose Option 3 i.e., SUBMIT from main Batch Screen.
We need tp prepare aan ADDSCL to compile a program through Endeavor.The following points to be noted while preparing ADDSCL.
1.In which environment are we going to add a program.?As you all know there are different environments in Endeavor such as Production, Test, Accpetance, QuickFix Etc., and it is installation dependent.
2.Select the environment, say if you are adding a program in Test environment
3.Goto Test environment => Choose option Batch => Build SCL => ADD/Update SCL => here we need to give CCID, Processor Group, Override signout(Y/N), Replace Member(Y/N), Element, Type, Comments Etc.,
And finally from which PDS we are adding an element.
4. PF3(2 times) --> leads to the Batch main screen
5. choose Option 2 in Batch main menu i.e., EDIT
6.Check the ADDSCL whether everything is correct.
7. Choose Option 3 i.e., SUBMIT from main Batch Screen.
$$
I think the question is how to compile an existing program in unit test or SIT or any region by Endeavor. If the question is just to complie the existing program but not to add the changes to Endeavor the following option can be used in Endeavor.
a. Use test Endeavor option.
b. Use forground option.
c. Go to 'Generate' option.
d. Mention the program name type and system name.
The program will be compiled in this region.
a. Use test Endeavor option.
b. Use forground option.
c. Go to 'Generate' option.
d. Mention the program name type and system name.
The program will be compiled in this region.
$$
Guys
Every application needs to setup in Endevor as System & Subsystem names.
Then each type like cobol jcl etc should need to be defined under that application in Endevor. Then the actual core work is there is a required processor to be setup for each type under each system in Endevor.
So when an user adds an element/cobol module in to Endevor stage1 it will pick the default processor which might the required processor to compile and linkedit it.
If you want to learn more about it check in Endevor main menu display option then in processor option after gone inside in to processor you can see the actual processor along with the variables.
Believe me guys Endevor is not a magic. The problem is people might not have enough access to see the internal things/ don't want to learn more.
I worked as an Endevor administrator and it is the best configuration product in mainframes.
Every application needs to setup in Endevor as System & Subsystem names.
Then each type like cobol jcl etc should need to be defined under that application in Endevor. Then the actual core work is there is a required processor to be setup for each type under each system in Endevor.
So when an user adds an element/cobol module in to Endevor stage1 it will pick the default processor which might the required processor to compile and linkedit it.
If you want to learn more about it check in Endevor main menu display option then in processor option after gone inside in to processor you can see the actual processor along with the variables.
Believe me guys Endevor is not a magic. The problem is people might not have enough access to see the internal things/ don't want to learn more.
I worked as an Endevor administrator and it is the best configuration product in mainframes.
$$
To compile a program through Endeavor. We need tp prepare an ADDSCL to compile a program through Endeavor.The following steps to be needed while preparing ADDSCL.- In which environment we are going to add a program.
- Select the environment say if you are adding a program in Test environment.
- Goto that environment => Choose option Batch => Build SCL => ADD/Update SCL => here we need to give CCID Processor Group Override signout(Y/N) Replace Member(Y/N) Element Type Comments Etc. And finally from which PDS we are adding an element.
- PF3(2 times) --> leads to the Batch main screen.
- choose Option 2 in Batch main menu that is EDIT.
- Check the ADDSCL whether everything is correct.
- Choose Option 3 that is SUBMIT from main Batch Screen.
$$
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.
• 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 . This will bring up a list of all available systems. Select the desired system by tabbing down to the left of the desired system place a 'S' there and . This will display the current order in which elements will be processed in the package.
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
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 . This will bring up a list of all available systems. Select the desired system by tabbing down to the left of the desired system place a 'S' there and . This will display the current order in which elements will be processed in the package.
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
http://mainframesinfo4u.blogspot.com/2009/08/endevor-actions-submiting-scl.html
$$
