Edditing Spool Files for Open System Jobs

[Keith Grizzell]

​In ESP is there a way to edit what information is contained in the spool file for open system jobs. The jobs are in application's run by the ESP scheduler and produce a spool file at the end of execution. We have a request from some developers to include more information in these spool files and they say that the spool files contained more information at a previous employer . Not exactly sure what they are asking for, possibly log information or communication info when jobs fail but I have included a typical example of one of our current spool file

----------------------------------------------------------------

Output of messages for workload object OSPDH001/PRODMAIN.4407/MAIN

Start date Mon Jun 10 19:06:10 2019

----------------------------------------------------------------

C:\Program Files\CA\WA Agent>REM OSPDH001.bat

C:\Program Files\CA\WA Agent>REM @echo off

C:\Program Files\CA\WA Agent>REM Move to D:\CYB_Jobs Directory

C:\Program Files\CA\WA Agent>D:

D:\>CD "\CYB_Jobs"

D:\CYB_jobs>IF NOT 0 EQU 0 GOTO DONE

D:\CYB_jobs>REM Execute SAP package.

D:\CYB_jobs>"D:\IPSsp7\SAP BusinessObjects\Data Services/bin/AL_RWJobLauncher.exe " "C:\ProgramData\SAP BusinessObjects\Data Services/log/JobServer_1/" -w "inet:HQCLAPP52:3500" -C "C:\ProgramData\SAP BusinessObjects\Data Services/log/JOB_ETL_All_DataHub_GRG_wReplication.txt"

Warning: ORB::BOA_init: hostname lookup returned `localhost' (127.0.0.1/::1)

Use the -OAhost option to select some other hostname

D:\CYB_jobs>REM Set Error Level in ESP

D:\CYB_jobs>"C:\Program Files\CA\WA Agent\SetExitC" 0

------------------------------
Lead Operator
Grange Insurance
------------------------------

[Jonathan Calloway]

Keith,

First off, it appears that the spool file you have used in your example is form a Windows job, not from an Open Systems job.  Unless I'm incorrect, Open Systems generally refers to anything *NIX, like AIX or Linux.

Either way, anything that you send to STDOUT or STDERR will go to the spool file.  Developers can write their scripts and customize this, determing what gets sent to ESP via spool output or what goes to their log files.

Just remember that the more you "dump" into spool files, the more your spool folder fills. So there is a risk that you'll run out of space on whatever file system your spool file is in.  You can control this, of course, by rotating your spool files.  There are configurations available for this in the agent parm file.

Hope this is helpful!

<JC>​

[Keith Grizzell]

JC,

Thanks for your response. You are correct, the spool file is from a windows job. The reason I was asking is that the developers were asking us what we needed to do on our end so they could get more information into the spool files. It was there contention that we controlled all the information that goes put into the spool file and wanted us to "turn on" more features. 

Thanks,
Keith

------------------------------
Lead Operator
Grange Insurance
------------------------------

[Jonathan Calloway]

​Keith,

Your devs are in complete control.  They can design their spool output to be as informative or as sparse as they want.  In our environment, our Unix admins tightly control this through templates they provide to the developers.  However, our Windows admins are not as concerned, so we have some spool output that is 30 pages long!  I have been communicating this to our devs for a while now, and some of them are actually working to design spool output that is helpful to them.

Good luck!
<JC>