The NOSUSPEND option

The default action for certain commands is to suspend the application until the required resource becomes available. You can use the NOSUSPEND option to inhibit this wait and return to the next instruction in the application program.

The default action for the ENQBUSY, NOJBUFSP, NOSPACE, NOSTG, QBUSY, SESSBUSY, and SYSBUSY conditions is to suspend the execution of the application until the required resource (for example, storage) becomes available, and then resume processing of the command. The following commands can result in these conditions:
  • ALLOCATE
  • ENQ
  • GETMAIN
  • WRITE JOURNALNAME
  • WRITE JOURNALNUM
  • READQ TD
  • WRITEQ

You can use the NOSUSPEND option (also known as the NOQUEUE option for the ALLOCATE command) to inhibit this wait and cause an immediate return to the instruction in the application program that follows the command.

CICS® maintains a table of conditions referred to by the HANDLE CONDITION and IGNORE CONDITION commands in a COBOL application program.

Restriction: HANDLE CONDITION and IGNORE CONDITION commands are supported only in COBOL, PL/I, and assembler language applications (but not AMODE(64) assembler language applications). They are not supported in all other supported high level languages.
Execution of these commands either updates the existing entry, or causes a new entry to be made if the condition has not yet been the subject of such a command. Each entry indicates one of the following three states:
  • A label is currently specified:
    HANDLE CONDITION condition(label)
  • The condition is to be ignored:
    IGNORE CONDITION
  • No label is currently specified:
    HANDLE CONDITION
When the condition occurs, the following tests are made:
  1. If the command has the NOHANDLE or RESP option, control returns to the next instruction in the application program. Otherwise, the condition table is scanned to see what to do.
  2. If an entry for the condition exists, this entry determines the action.
  3. If no entry exists and the default action for this condition is to suspend execution:
    • If the command has the NOSUSPEND or NOQUEUE option, control returns to the next instruction.
    • If the command does not have one of these options, the task is suspended.
  4. If no entry exists and the default action for this condition is to abend, a second search is made looking for the ERROR condition:
    • If found, this entry determines the action.
    • If ERROR is searched for and not found, the task is abended.


dfhp3_perf_nosuspend.html | Timestamp icon Last updated: Monday, 5 June 2017