MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » June 2014

Re: BRMS - Simple method to determine and track volume and/or drive errors - CPP630C *Attention* Media error detected by device TAPMLB01



fixed

On 09-Jun-2014 12:25 -0500, Steinmetz, Paul wrote:
<<SNIP>> The CPP630C msg actually does not contain the volume that
had the error. <<SNIP>>

In some cases, the message data prepared by the OS programs may be somewhat generic [most likely when issued by the same program], even if any one particular message does not expose all of the information that the program maintains. With an assumption that some other generic information might be available from that specific message in the given scenario, the following might be a way to check for that data, knowing that an otherwise very similar[ly coded] message cpf630d *does include* the desired Volume identifier:

crtmsgf myLib/mycpfmsg
mrgmsgf qcpfmsg tomsgf(myLib/mycpfmsg) select(cpp630c)
chgmsgd cpp630c msgf(myLib/mycpfmsg) FMT((...)...(...)) /* adding all of the additional Message Data Fields Formats (FMT) that appear in the message cpp630d, but do not exist yet in cpp630c */
wrkmsgd cpp630c msgf(qtemp/qcpfmsg) /* 2=Edit, append &43 to either the first or second level text; e.g.: &N Tape Volume: &43 */

Then during runtime, prior to the displaying the message, issue the following override request:

ovrmsgf qcpfmsg myLib/mycpfmsg

Note: All of the above can be done in the same job wherein that message was logged previously, i.e. after-the-fact, or [because the noted message is most likely viewed in QSYSOPR rather than an active joblog, done in any job that would use F1=Help on the message that was sent to the non-program Message Queue (MSGQ). And in either case, the library for the message file can be QTEMP.

Caveat: The above is unlikely to help however, because the length of overall message data in cpp630c is probably [still] much shorter than the data defined in cpp630d. And as such, very likely the OS program sending the message explicitly limits the amount of data sent; i.e. only as much data that is defined in the message, may be the length specified for the message-data-length provided on the Send Program Message request, regardless the amount of data defined and available may be greater.






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact