Transferring BRMS backup joblogs from FSFC target partition to FSFC source partition automatically

If the FSFC target is going down immediately following completion of the backup there is a way to move a joblog back to the FSFC source system. Beginning in the 7.3 version of the toolkit, the BRMS logging directory /QIBM/UserData/BRMS/logs is brought back from the target LPAR to the source LPAR and placed into /QIBM/UserData/BRMS/logs/fsfc/. Note that this directory is overwritten each time. The intent is to bring back the information about the most recent BRMS activities from the target LPAR. If you would like to bring back other information from the target LPAR (like the backup joblog) to the source LPAR, it can be placed into /QIBM/UserData/BRMS/logs.

A program could be written and called from an *EXIT in the BRMS control group to generate the joblog and copy it do the /QIBM/UserData/BRMS/logs directory or two *EXITs could be utilized directly in the control group entries. Either way the joblog must be generated and copied to /QIBM/UserData/BRMS/logs. The commands are similar to the following:

DSPJOBLOG OUTPUT(*PRINT)

CPYSPLF FILE(QPJOBLOG) TOFILE(*TOSTMF) JOB(*) TOSTMF('/QIBM/UserData/BRMS/logs')

For more information on using CPYSPLF to copy a spooled file to a STMF in the IFS see technical document N1011580: 'New CPYSPLF Function to Copy SPLFs to Stream Files in the IFS'

Now when the ENDSYSCPY happens and the toolkit transfers QUSRBRM and /QIBM/UserData/BRMS/logs back to the FSFC source partition the joblog will be copied into /QIBM/UserData/BRMS/logs/fsfc/.

Collect and send the BRMS flight recorders (the complete /QIBM/UserData/BRMS/logs directory) to IBM for analysis.