BND7903E GETDSN SSOB failure RC=1C

Products

• Bundl

Issue/Introduction

The Bundl collector is issuing a "BND7903E GETDSN SSOB failure, RC=1C" error message.

What is the cause of this error and how to identify the "bad" DSF record?

Cause

An invalid value has been coded in the "INPUT Dsname" field of a Bundl DSF record.

When this error is received, the report will not be collected by Bundl, and will be left in the JES2 queue.

Resolution

The '1C' indicates a "bad" DSF record is being used to collect the report. Typical causes are things like an invalid DESTINATION or WRITER field coded in the DSF record. Check with the Bundl Administrator/Users to see what changes may have recently been made to the DSF records. Then check the DSF records themselves and it should be possible to identify the invalid field in the record that's causing the error and get it corrected.

Additional Information

There may not be an "easy way" to determine the problem DSF record.

To get a hard copy listing of all of the DSF records, run the CC50J098 utility with a 'Y' specified in offset/column 6 of the DMPB098 control PARM. Having a hard copy listing of the "INPUT Dsname" field in all the DSF records might help identify the problem record.

The BND7065I message that specifically points to a particular DSFID and SEQNO may be misleading, in that it does NOT necessarily point specifically to the problem DSF record. For example, if there was a BND7065I message on DSFID=xxxx ; SEQNO=726, and another BND7065I message on DSFID=xxxx ; SEQNO=728, and the "BND7903E GETDSN SSOB failure RC=1C" was received in between the two, then the "BAD" DSF record would likely be SEQNO=> 727 of that same DSFID.

Within the DSF record itself, the type of thing to look for to identify it as the "BAD" DSF record usually has something to do with how the "INPUT Dsname" is coded. And, as per this article, the usual "invalid" fields coded in the  INPUT DSNAME field are the DESTINATION or WRITER fields. For example, an invalid WRITER would be one that contains more than eight characters. That would be the type of thing to look for to identify the "BAD" record.

The following excerpt from the Bundl documentation outlines OTHER possible fields that could have been coded in the INPUT Dsname field that may have been specified INCORRECTLY and that would cause the "BND7903E GETDSN SSOB failure RC=1C" message to be received: