MFS ENDEVOR PROCEDURES

 

 

GENERAL INFORMATION:

Endevor will maintain the source code only, for the MFS(s).

TYPE = MFS   PrGrp = MFS 

 

The Endevor Generate option “G” will be used to manipulate the source in Endevor, but it will not execute the IMS MFS Utilities, which will be referred to as MFSGEN.

 

The MFSGEN to get the screens into the IMS region will be performed OUTSIDE Endevor.

See “TSO MFSGEN Information:” below for more details.   

 

PRODUCTION MOVES:

You will create a package to get the source into Production, once the MFS package has executed successfully, send a  Move Form to [email protected],  Virginia will perform the actual MFSGEN to the Production IMS Region.  

Therefore, DO NOT put MFS  Source in a Package marked for 17:30 execution.

 

PRODUCTION LISTINGS:

Browse by member name outside of Endevor in DHR.BDA.BDA.PROD.MFS.LISTING

 

TSO MFSGEN INFORMATION:

Sample MFSGEN JCL is in DHR.BDA.PROD.JOBLIB:  MFSTEST and MFSUSER.

This sample will gen to both the FORMAT and TFORMAT libraries.

You can copy and use this, or change your existing MFSGEN JCL as follows: 

 

Remove the Librarian Step:

//**                                                       

//LIBRA   EXEC LIBR                                       

//LIBR.MASTER DD DSN=DHR.BDA.TEST.SOURCE,DISP=SHR        

//LIBR.SYSIN DD *                                         

-OPT LIST                                                 

-SEL member                                             

-EMOD                                                     

-END                                                      

//**                                                      

 

 

Remove this Librarian Statement:

//ZZZ0001S.SYSIN DD DSN=*.LIBRA.LIBR.OSJOB,DISP=(OLD,DELETE)  

 

Add these two Endevor Statements:

//ZZZ0000S.DD01 DD DSN=DHR.BDA.BDA.DEV2USER.MFS(member), DISP=SHR

//ZZZ0001S.SYSIN DD DSN=DHR.BDA.BDA.DEV2USER.MFS(member),DISP=SHR     

where (member) = the name of  the mfs source module.

DEV2USER will need to be changed to USER2PRD for the IMTA and IMXA regions.

 

TEAM56 – EIS ONLY:

If not using the BDA line, you will need to change the BDA.BDA reference to the appropriate pdm, BDA.PDM*.    Also change the parm PDM=BDA, to the appropriate pdm, this will perform rename from EJA to EXA or EXB processing.    Make sure to use corresponding regions: TT, TA, XT and XA, based on the PDM used.