Activating the IOACND Utility (and Examples)

The IOACND utility can be activated as a step in a job or from an application program (as illustrated in the following examples). In these cases, proper protocol is ensured. However, if you use a different method to invoke the IOACND utility, follow the rules below to ensure that the proper protocol is maintained:

• When the IOACND utility receives control, register 1 must contain the address of a full word.
• To indicate this is the last, and only, parameter, the high-order byte must contain X'80'.
• The three low order bytes of the fullword must contain the address of a halfword field.
• The halfword field must be the count of the number of bytes of information contained in the parameter list.
• The parameters must immediately follow the halfword field.
  • As a job step

    //CND1 EXEC IOACND
  ADD COND JOB-A-ENDED-OL 0505
  DELETE COND JOB-A-DID-NOT-RUN 0505
  CHANGE RESOURCE TAPE -1
  ADD RESOURCE INIT-CPUA 3
  DELETE RESOURCE INIT-CPUB
  ADD CONTROL PROD-DATA-BASE E

  • As a job containing AutoEdit variables, submitted through the Control-M monitor

    //CND1 EXEC IOACND
  ADD COND     AR-FILE-009-CREATED  %%OMONTH.%%ODAY

  • As an operator command

    S IOACND,PARM='ADD COND END-CICS 0102'

  • As a called procedure in an application program

             CALL CTMCND,(PARMCOND),VL
         LTR  R15,R15
         BNZ  ERROR
         ...
PARMCOND DC   AL2(80)
DC   CL80'ADD COND CICS-FILE-CLOSED 0102'

  • As invoked from a REXX exec

    parm = ’ADD COND cond_name odat’
address linkmvs ’ioacnd parm’

Note: Program IOACND works in 24-bit addressing mode and is reusable and reentrant.