The holder address space TAURHLD is used to install the SVC routine and to set up a common access data space that contains user administration control structures needed for communication.
The type 3 SVC routine is installed whenever the address space starts, and is deleted from the system SVC table when it is stopped.
Customize the sample JCL procedure that is used to start the holder. This is located in hlq.ZSERVER.JCL(IVPHOLD) and needs to be copied to the PROCLIB concatenation.
Outlined below is the content of IVPHOLD. Verify and customize the high level qualifier defined for TAURHLQ:
//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
The TAURHOLD procedure statement has been changed and now defines one new parameter, which is used in the TAURHOLD exec statement:
The CONFXML and CONFOSR DD statements have been added to support the new XML configuration file. CONFXML defines the XML configuration member to use, which you can customize, and CONFOSR defines the OSR (Optimized Schema Representation), which is used to validate the XML configuration file; this must not be changed.
The CONFIG DD statement has been commented out as this was used for the legacy configuration files. If you have both the legacy and new configuration file DD statements active, the holder will not start and you will see the following error message in the MAINTASK DD:
ZCF0059E 11:08:45.603 Definition of old and new configuration is not allowed.