z/OS V1R6.0 DFSMS Access Method Services for Catalogs

Chapter 2. Modal CommandsWith Access Method Services, you can set up jobs to execute a sequence of modalcommands with a single invocation of IDCAMS. Modal command executiondepends on the success or failure of prior commands.In this chapter you will find:vvvModal commandsCondition codesExamples of how to use modal commands.Modal CommandsYou cannot use these commands when Access Method Services is running in TimeSharing Option (TSO).vvvvvvIF-THEN-ELSE command sequence, which controls command execution on thebasis of condition codesNULL command, which causes the program to take no actionDO-END command sequence, which specifies more than one functional accessmethod services command and its parametersSET command, which resets condition codesCANCEL command, which ends processing of the current job stepPARM command, which chooses diagnostic aids and options for printed output.Commonly used single job step command sequencesA sequence of commands commonly used in a single job step includesDELETE-DEFINE-REPRO or DELETE-DEFINE-BLDINDEX.vvYou can specify either a data definition (DD) name or a data set name withthese commands.When you refer to a DD name, allocation occurs at job step initiation. Theallocation can result in a job failure, if a command such as REPRO follows aDELETE-DEFINE sequence that changes the location (volser) of the data set.(Such failures can occur with either SMS-managed data sets ornon-SMS-managed data sets.)Avoiding Potential Command Sequence FailuresTo avoid potential failures with a modal command sequence in your IDCAMS job,perform either one of the following tasks:vvSpecify the data set name instead of the DD nameUse a separate job step to perform any sequence of commands (for example,REPRO, IMPORT, BLDINDEX, PRINT, or EXAMINE) that follow a DEFINEcommand.© Copyright IBM Corp. 1973, 2004 17