Introduction:
The sample procedures below can be used to ADD tasks, DELETE tasks, or modify the processing criteria for the CADZSPLx and CADDSAPx (SAPI) tasks.
Dispatch, 11.7, CADDSPLx, CADZSPLx, VSGMU105, ADD, CHANGE, DELETE
N/A
Instructions:
In EXAMPLE 1, The MSG and ARCH tasks had not yet been compiled into the CADZSPLx tasks ROOT LDS by the DDEXLDSI job when the product and LDS files were initially installed.
We will be adding the MSG and ARCH task processing criteria into the CADZSPLx ROOT LDS as new tasks...
------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------
EXAMPLE 1:
/F SPLx,ADD MSG,CLASS=S,A=NOI
* The DEST parameter on an ADD statement is OPTIONAL and not required.
You should see the following messages:
CADD110I SPLx Operator=ADD MSG,CLASS=S CADD650I SPLx Adding/Updating Class/Dest information for MSG CADD651I SPLx Class/Dest information stored into CADDSPLx
To add the ARCH task and the SAPIARCH tasks processing criteria for CLASS=W and DESTINATION=WXYZ, issue a:
/F SPLx,ADD ARCH,CLASS=W,DEST=WXYZ,A=INTERCEPT
You should see the following messages:
CADD110I SPLx Operator=ADD ARCH,CLASS=W,DEST=WXYZ,A=INTERCEPT CADD650I SPLx Adding/Updating Class/Dest information for ARCH CADD651I SPLx Class/Dest information stored into CADDSPLX
** You do not have to issue any commands to add the associated SAPI tasks. The processing criteria for the SAPI tasks will be added automatically by the above adds for MSG and ARCH.
If you want, bring down Dispatch first and then do a recycle of the CADZSPLx task and verify the MSG and ARCH tasks are now listed in your CADZSPLx task startup messages. Then bring Dispatch back up and go to the VOPMI100 screen and restart the MSG and ARCH tasks. Then try starting the SAPIMSG and SAPIARCH tasks.
------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------
In EXAMPLE 2, we will be deleting and re-adding the RPI2/SAPIRPI2 tasks with the new processing criteria of Class=V and Destination=MGM...
EXAMPLE 2:
/F SPLx,DEL RPI2
You should see the following messsages:
CADD110I SPLx Operator=DEL RPI2 CADD652I SPLx Removing Class/Dest information for RPI2 CADD008I SPLx RPI2 Class V Dest MGM has been deleted CADD653I SPLx Class/Dest information removed from CADDSPLx
** You do not have to issue any commands to delete the SAPIRPI2 task. The processing criteria for the SAPIRPI2 task will be deleted automatically by the above delete for the RPI2 task.
To re-add the RPI2 task and the SAPIRPI2 tasks with the new processing criteria, issue a:
/F SPLx,ADD RPI2,CLASS=V,DEST=MGM,A=INTERCEPT
You should see the following messages:
CADD110I SPLx Operator=ADD RPI2,CLASS=V,DEST=MGM,A=INTERCEPT CADD650I SPLx Adding/Updating Class/Dest information for RPI2 CADD651I SPLx Class/Dest information stored into CADDSPLX
-------------------------------------------------------------------------------------------------
** IMPORTANT NOTE **
After modifying the CADZSPLx tasks processing criteria, do not forget to also update the Dispatch "VSGMU105 - Dedicated Sysout Control Information Screen", which can be accessed via option 9.0 from the Main Menu. Code the Dispatch CLASS and/or DEST processing criteria for the RPI1,2,3,MSG and ARCH tasks to MATCH those that are defined for the corresponding CADZSPLx tasks. After updating the Dispatch VSGMU105 screen, in order to affect any changes, you will need to either recycle the modified subtask(s) individually or recycle the Dispatch STC.
-------------------------------------------------------------------------------------------------