Life cycle of START Command in CICS as follows. START command executes through ATI (Automatic time ordered transaction initiation)
- A user task issues a START command that’s processed by interval control.
- Interval control creates an ICE that indicates the trans-id, expiration time, and terminal-id for the task to be started.
- If data is passed to the started task, interval control invokes temporary storage control to save that data.
- Temporary storage control saves the data in the temporary storage file.
Different START commands:
A command that schedules a task for immediate execution
EXEC CICS
START TRANSID(‘LST1’)
END-EXEC.
A command that attaches the task to a terminal
EXEC CICS
START TRANSID(‘LST1’)
TERMID(‘L86R’)
END-EXEC.
A command that uses the TIME option to specify an expiration time
EXEC CICS
START TRANSID(‘LST1’)
TIME(‘170000’)
END-EXEC.
A command that uses the INTERVAL option to specify an expiration time
EXEC CICS
START TRANSID(‘LST1’)
INTERVAL(001600)
END-EXEC.
A command that uses the AT option to specify an expiration time
EXEC CICS
START TRANSID(‘LST1’)
AT HOURS(10) MINUTES(45)
END-EXEC.
A command that uses the AFTER option to specify an expiration time
EXEC CICS
START TRANSID(‘LST1’)
AFTER MINUTES(1) SECONDS(32)
END-EXEC.
A command that passes data to the started task
EXEC CICS
START TRANSID(‘LST1’)
FROM(ITEM-NUMBER1)
END-EXEC.
Also read
- BMS mapset logic to create HTML template - The shortcut and direct way to identify if the given BMS mapset is generating HTML template or not in CICS programming
- TDQ in CICS different types real project usage - The TDQ in CICS has many advantages. They are two types. Explained why they need in CICS programs
- CICS TSQ are task independent why you need - The storage queues in CICS are very in need and out of these TSQ has lot of benefits so that you can create it dynamically and delete it. If you want, you can write and modify the records written to it.
