OnDemand Users Group

Support Forums => CMOD for z/OS Server => Topic started by: LWagner on April 22, 2011, 06:00:01 PM

Title: How to read attached documents in the system log
Post by: LWagner on April 22, 2011, 06:00:01 PM
The system log table has attached documents, referenced in column DOC_NAME.  Can these be accessed and read programmatically.  The MSG_TXT column is varchar, but only shows about 80 bytes.   Is it possible to get at all this information ?

TIA,

By the way, we're finally about to go live with 8.4.0.3

Larry
Title: Re: How to read attached documents in the system log
Post by: Justin Derrick on April 23, 2011, 01:31:21 PM
Unfortunately, you need to retrieve the associated document and parse through it. 

With the newer versions of CMOD on Multiplatforms, there are both longer MSG_TXT fields (from 255 char to 2048 varchar), new message numbers with more info, and even a 'Load Log' which contains tons of information about document loads.
Title: Re: How to read attached documents in the system log
Post by: LWagner on May 15, 2011, 01:17:22 AM
We get about 90 "semi-failed" document uploads nightly, msgnum 88.  But most or all do not include document unloads.

I want to set up an automatic read process of the attached documents to scan the text to determine the actual number of rows loaded and whether the documents were unloaded or not.

It sounds like the this is a custom application, since one needs SQL to get the syslog messages, then other API or DOCGET calls to pick up the text to read and parse.

That would be so useful to have as part of administration tools.
Title: Re: How to read attached documents in the system log
Post by: Justin Derrick on May 08, 2012, 12:59:12 PM
Quote from: LWagner on May 15, 2011, 01:17:22 AM
I want to set up an automatic read process of the attached documents to scan the text to determine the actual number of rows loaded and whether the documents were unloaded or not.

It sounds like the this is a custom application, since one needs SQL to get the syslog messages, then other API or DOCGET calls to pick up the text to read and parse.

That would be so useful to have as part of administration tools.

I'm not sure if you have the "arslog" logging exit in z/OS -- but if you do, I'd use that to check for message number 88, and either write the log output you're interested in to a file, or take some specific action (like issuing an unload, or trying again).