Basic migration of the holder address space JCL (TAURHLD)

Below is an example of the holder JCL. The changes required are highlighted in bold:

//TAURHOLD PROC P1=
//TAURHLQ  SET  TAURHLQ=hlq.ZSERVER 
//*-----------------------------------------------------------------* 
//*- RUN ZSERVER HOLDER TASK                                       -* 
//*-----------------------------------------------------------------* 
//TAURHOLD EXEC PGM=TAURHOLD,TIME=NOLIMIT,PARM='/&P1,,'
//STEPLIB  DD DISP=SHR,DSN=&TAURHLQ..AUTHLIB  
//SYSEXEC  DD DISP=SHR,DSN=&TAURHLQ..REXX  
//CONFIG   DD DISP=SHR,DSN=&TAURHLQ..CONFIG(IVPHOLD)
//*CONFXML  DD DISP=SHR,DSN=&TAURHLQ..CONFIG(IVPXML)
//*CONFOSR  DD DISP=SHR,DSN=&TAURHLQ..OSR(IVPOSR)
//SYSPRINT DD SYSOUT=*  
//SYSTSPRT DD SYSOUT=*  
//SYSOUT   DD SYSOUT=*  
//DSPPRT   DD SYSOUT=*,LRECL=255  
//SYSTSIN  DD DUMMY 
//         PEND

The TAURHOLD procedure statement has been changed and now defines one new parameter, which is used in the TAURHOLD exec statement:

• P1 is used to specify if tracing should be enabled while reading the XML configuration file. Do not change this unless asked to do so by a member of Micro Focus SupportLine staff.

The CONFXML and CONFOSR DD statements are only required if you want to use the new XML configuration file. If you want to use your existing configuration files, these can be commented out or otherwise disabled.

The CONFXML DD statement points to the XML configuration member. Information on how to configure z/Server using XML can be found in Configuring z/Server.

The CONFOSR DD statement points to the Optimized Schema Representation (OSR) that is used to validate the XML configuration file.

There is also an additional final PEND statement.