Linking a program creates a load member in the appropriate Endevor Stage U load library and saves the link edit listing. If the program is standalone, the link occurs during the GENERATE process -- that is, when you ADD it to Stage U or do a GENERATE WITH COPYBACK into Stage U, you are compiling and linking the program; therefore, to put this kind of program into production, nothing more is needed than outlined in the section V, above. But if the program must be linked with other application modules, the link must be done as a separate step, using linkcards. Currently, all online programs use linkcards.
When the element (program or linkcard) is moved to Endevor stage C via a package, the load module is moved from the Stage U load library to the appropriate Stage C libarary - BATCH.OT.END.LOADLIB (for batch programs) or PROD.OT.END.IMSLOADT (for online programs).
1. LINKCARDS.
Endevor has LINKCARDS for every STATIC circle. The linkcards are in PROD.OT.END.LINKCTL or PROD.OJ.LF.END.LINKCTL and contain the INCLUDE statements for every OBJ member in a static circle.
The LINKCARDS and their associated link PROCESSOR GROUPS ARE LOCATED N 5f OF THIS DOCUMENT. (Explanation and/or view listing of the processor groups).
2. LINK AN EXISTING LINKCARD (MOST COMMON SCENARIO).
a. The obj concatenation order is Stage U, Stage C, Stage 1, and Stage 2. Make
sure you are including obj’s from the correct libraries.
b. If you are making CHANGES to the linkcard, retrieve it from Stage C
to yourid.LIB.LINK (or library of your choice)and complete the changes. Add the revised linkcard to Stage U using the instructions for adding a new linkcard (section VII.3,below).
c. If you DID NOT change the linkcard, generate it to Stage U in batch, as follows: (for screen layouts refer to item 4 ahead)
• Select option 3 - BATCH.
• Build the SCL as you do for programs.
• On the SCL generation screen, select Option 4 - GENERATE.
• On the generate screen, select copyback = Y.
• Build using map = Y.
• When done, submit the job using jobname OTXX94# & msgclass H
for (SDSF).
This process is the same as for generating (recompiling) programs; for more detail, see section VI.1.
d. Check the output in SDSF. Max down to the bottom. Verify that the module
was marked as Reentrable/Reusable with AMODE=31 and RMODE=ANY. Load modules
now reside in the appropriate Stage 1 load library. Verify that your OBJs were included and that origin of all other obj’s is correct.
e. Once you have verified that the add job ran successfully, move the link card to Stage C, using Option 4 - PACKAGE (from the Endevor Primary Options menu). This process is the same as for moving programs to Stage C; for greater detail, see sections V.7.a through f, above.
3. ADD A NEW LINKCARD
a. A new LINKCARD must be ADDED to Stage U with the correct processor
group for each system. Below is a sample processor group only! Do not assume this is the processor for your new linkcard.
---------------------------- 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 ===> OTXXXXXX NEW VERSION ===>
TYPE ===> LINKCARD OVERRIDE SIGNOUT ===> N (Y/N)
STAGE: U PROCESSOR GROUP ===> LEB2IL47
UPDATE IF PRESENT ===> N (Y/N)
COMMENT ===>
FROM ISPF LIBRARY: LIST OPTIONS:
PROJECT ===> OTXX94 DISPLAY LIST ===> Y (Y/N)
LIBRARY ===> LIB
TYPE ===> CNTL
MEMBER ===> OTAA2FPP THRU MEMBER ===>
FROM OTHER PARTITIONED OR SEQUENTIAL DATA SET:
DATA SET NAME ===>
-------------------------------------------------------------------------
b. Submit the newly generated SCL. Check the output in SDSF. Max down to the
bottom. Verify that the module was marked as Reenterable/Reusable with
AMODE=31 and RMODE=ANY. Load modules now reside in the appropriate stage U
load library. Verify that your OBJs were included.
c. Once you have verified that the add job ran successfully, move the link card to Stage C, using Option 4 - PACKAGE (from the Endevor Primary Options menu). This process is the same as for moving programs to Stage C; for greater detail, see sections V.7.a through f, above.
Procedures on how to generate a link without changes follow on the next page.
Custom Search
