Maximize CSM implementation
Question: I regularly shut down an object (for example, CICS) at a scheduled period each day.
Batch maintenance processing for that object takes place during that shutdown period (for example, file backups or database reorganizations). I want to have the object automatically start back up when the maintenance processing is complete. What’s the best way to do this?
Answer: Add a step to the end of the batch maintenance job to run IMFSUBEX. Use this additional step to schedule CSMACT for the object.
See the MainView AutoOPERATOR Advanced Automation Guide for information on IMFSUBEX usage.
Schedule the CSMACT EXEC by entering
CSMACT object_name UPEARLY NOREQ
Make sure you specify UPEARLY and not UP.
Question: I need to bypass MainView AutoOPERATOR and CSM control of the system startup on occasion. How can I accomplish this?
Answer: CSM startup is triggered by message PM0010I. When that message is issued, it schedules the EXEC ACMM000. ACMM000 calls CSMINIT and so on.
To bypass AO/CSM control of the system, you could write a small EXEC that based on the reply to a WTOR, schedules or does not schedule ACMM000 with an IMFEXEC SELECT EXEC statement; for example:
'IMFEXEC WTOR 'DO YOU WANT CSM TO START THE SYSTEM? REPLY ''Y'' TO',
'START.' WAIT(60) REPLY(REP)'
IF IMFCC = 8 THEN DO
'IMFEXEC WTO 'TIME HAS BEEN EXCEEDED. CSM WILL NOT START SYSTEM.''
'IMFEXEC EXIT CODE(0)'
EXIT
END
IF REP = 'Y' THEN DO
'IMFEXEC SELECT EXEC (ACMM000)'
END
ELSE DO
'IMFEXEC WTO 'CSM WILL NOT START SYSTEM.''
END
'IMFEXEC EXIT CODE(0)'
EXIT
After writing this EXEC (or something similar), change Rule ID ACMRC005 in Rule Set AAORULBC to schedule this new EXEC instead of ACMM000.
Remember, anytime a PTF performs maintenance against AAORULBC, Rule ID ACMRC005 must be changed to call the EXEC, instead of ACMM000.