I’ve always logged in as SAGUSER post every IPL and started cor.sh manually since we installed the Data Archival product several years ago. Ok, I am finally tired of doing that!
The COR daemon and ADR extractor and accumulator run over on the OMVS side of z/OS, and Software AG is very nice to include in the libraries JCL samples for doing COR startup and shutdown from a batch job:
//COR JOB CLASS=K,MSGCLASS=X //COR EXEC PGM=BPXBATCH,REGION=0M, // PARM='pgm /opt/softwareag/cor/v828/INSTALL/cor.sh start' //STDOUT DD SYSOUT=* //STDERR DD SYSOUT=* //CORSTOP JOB CLASS=K,MSGCLASS=X //COR EXEC PGM=BPXBATCH,REGION=0M, // PARM='pgm /opt/softwareag/cor/v828/INSTALL/cor.sh stop' //STDOUT DD SYSOUT=* //STDERR DD SYSOUT=*
So, since these are batch jobs, I can automate this, right?
However, CA-7 doesn’t have my SAGUSER info defined, and the password changes every 90 days and would need constant maintenance by our sysprogs. But these jobs have to run as SAGUSER in order to have proper access to the OMVS file system and to set proper ownership to the output files there. I don’t think we can just set USER=SAGUSER on the job card and let our production control ID submit it and expect that to work.
For anyone out there who has automated the startup and shutdown of the COR and COR daemon processes, what did you do?
Thanks in advance!