Endevor message "BSTPMOIO: F001 $BPRINT FAILED FOR FILE ddname - REASON OPEN ERR"

Products

• Endevor

Issue/Introduction

Endevor batch utilities like C1BM3000 or C1BR1000 might issue error message

BSTPMOIO: F001 $BPRINT FAILED FOR FILE ddname  - REASON OPEN ERR

In the message, 'ddname' could be any ddname used to produce  endevor printed output, like C1MSGS1 or BSTRPTS

Cause

This message has two possible causes

• The OPEN operation for 'ddname' failed for some reason
• It was not possible to acquire storage needed to access the file

Resolution

Very often this is caused by a JCL error. The DD statement for 'ddname' is missing.

MVS normally displays messages showing the cause of the failed OPEN. They print to SYSMSGS and/or JESMSGLG for the job

If the utility is being run from TSO, the ddname has to be allocated in the TSO logon procedure or via TSO ALLOCATE command (which is normally issued by the CLIST or REXX that runs the utility). In this case, the messages about the OPEN error will show up in SYSMSGS and/or JESMSGLG for the TSO session.

It is possible to have MVS echo the messages to the TSO screen by setting parameters in the TSO profile. To enable the messages, issue command TSO PROFILE WTPMSG MSGID from the ISPF command line before running the utility

MVS messages in the TSO screen are normally useful and informative but can also be disturbing. In case of need, they may be disabled by command TSO PROFILE NOWTPMSG