Using the TSO RECEIVE command creates the partitioned data set from the compressed XMIT file. This document takes hlq.ENDEVOR to be the installation prefix.
Enter TSO or Workstation commands below:
===> receive indsn('hlq.INSTALL.XMIT')
When prompted, type:
INMR906A Enter restore parameters or 'DELETE' or 'END' +
restore dataset('hlq.ENDEVOR.INSTALL.XMIT’)
You will receive the following messages:
COPY INDD=((SYS00031,R)),OUTDD=SYS00030 IEB1013I COPYING FROM PDSU INDD=SYS00031 VOL=USR001DSN= SYS11214.T134430… IEB1014I TO PDS OUTDD=SYS00030 VOL=USR002 DSN=hlq.ENDEVOR.XMIT IEB167I FOLLOWING MEMBER(S) LOADED FROM INPUT DATA SET REFERENCED BY SYS00031 IEB154I AWMMODEL HAS BEEN SUCCESSFULLY LOADED IEB154I CNTL HAS BEEN SUCCESSFULLY LOADED IEB154I COBOL HAS BEEN SUCCESSFULLY LOADED IEB154I LOAD HAS BEEN SUCCESSFULLY LOADED IEB154I NDVRECE HAS BEEN SUCCESSFULLY LOADED IEB154I REXX HAS BEEN SUCCESSFULLY LOADED IEB154I REXXC HAS BEEN SUCCSESSFULLY LOADED IEB154I SKELS HAS BEEN SUCCSESSFULLY LOADED IEB154I SKELSC HAS BEEN SUCCESSFULLY LOADED IEB1098I 9 OF 9 MEMBERS LOADED FROM INPUT DATA SET REFERENCED BY SYS00031 … IEB147I END OF JOB - 0 WAS HIGHEST SEVERITY CODE INMR001I Restore successful to dataset 'hlq.ENDEVOR.INSTALL.XMIT'
The result is a partitioned data set with the following members:
BROWSE hlq.ENDEVOR.INSTALL.XMIT Volume: PROJ00 Command ===> Scroll: CSR Name Prompt Size Created Changed ID _________ AWMMODEL _________ CNTL _________ COBOL _________ LOAD _________ NDVRECE _________ REXX _________ REXXC _________ SKELS _________ SKELSC **End**
Each member except NDVRECE is a compressed data set:
| Member | Description |
|---|---|
| AWMODEL | The Endevor model file. |
| CNTL | JCL samples. |
| COBOL | COBOL sources which contain the Endevor API calls. |
| LOAD | LOAD library which can be used as the target library for the compile/link output of the COBOL sources. |
| NDVRECE | JCL to receive all other members. |
| REXX | REXX procedures to execute Endevor functions called from the Client via TCP/IP. |
| REXXC | Intended as a library for your customization on REXX procedures. |
| SKELS | ISPF Skeletons. |
| SKELSC | Intended as a library for your customization on ISPF Skeletons. |
You must use the TSO RECEIVE command again for the following members to create all necessary data sets:
| Member | Receive to PDS |
|---|---|
| AWMMODEL | hlq.ENDEVOR.AWMMODEL |
| CNTL | hlq.ENDEVOR.CNTL |
| COBOL | hlq.ENDEVOR.COBOL |
| LOAD | hlq.ENDEVOR.LOAD |
| REXX | hlq.ENDEVOR.REXX |
| REXXC | hlq.ENDEVOR.CUSTOM.REXX |
| SKELS | hlq.ENDEVOR.SKELS |
| SKELSC | hlq.ENDEVOR.CUSTOM.SKELS |
Member NDVRECE (already received) contains a receive sample batch job:
//STEP1 EXEC PGM=IKJEFT01
//SYSPRINT DD SYSOUT=*
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
RECEIVE INDSNAME('hlq.ENDEVOR.XMIT(REXX)') NONAMES
DATASET('hlq.ENDEVOR.REXX')
RECEIVE INDSNAME('hlq.ENDEVOR.XMIT(REXXC)') NONAMES
DATASET('hlq.ENDEVOR.CUSTOM.REXX')
RECEIVE INDSNAME('hlq.ENDEVOR.XMIT(CNTL)') NONAMES
DATASET('hlq.ENDEVOR.CNTL')
RECEIVE INDSNAME('hlq.ENDEVOR.XMIT(COBOL)') NONAMES
DATASET('hlq.ENDEVOR.COBOL')
RECEIVE INDSNAME('hlq.ENDEVOR.XMIT(LOAD)') NONAMES
DATASET('hlq.ENDEVOR.LOAD')
RECEIVE INDSNAME('hlq.ENDEVOR.XMIT(SKELS)') NONAMES
DATASET('hlq.ENDEVOR.SKELS')
RECEIVE INDSNAME('hlq.ENDEVOR.XMIT(SKELSC)') NONAMES
DATASET('hlq.ENDEVOR.CUSTOM.SKELS')
RECEIVE INDSNAME('hlq.ENDEVOR.XMIT(AWMMODEL)') NONAMES
DATASET('hlq.ENDEVOR.AWMMODEL')
/*
Verify that each RECEIVE has been successfully processed, for example, the SYSTSPRT output from the batch job should end with Restore successful for each type received:
Restore successful to dataset 'hlq.ENDEVOR.type'
You should give the received dataset containing the AWM model the low-level qualifier AWMMODEL. In the Team Developer perspective of Enterprise Developer a file mapping is defined for datasets with the low-level qualifier AWMMODEL which ensures that members of an AWMMODEL dataset are downloaded with the code page IBM-037. This ensures that special characters contained in the AWMMODEL member are correctly interpreted when the model is loaded on the client-side.
If you use another low-level qualifier for the model data set than AWMMODEL, you have to ensure that a corresponding file mapping is defined on the client-side.