If messages IEC130I DMMSGFIL DD STATEMENT MISSING and N28502 OPEN FAILED FOR VSAM ACB, CODE=X'80', DD=DMMSGFIL occur on the NetMaster region, how can this be corrected?
Article ID: 21632
Updated On:
Products
CMDB for z/OS
NetSpy Network Performance
NetMaster Network Automation
SOLVE
NetMaster Network Management for SNA
NetMaster Network Management for TCP/IP
NetMaster File Transfer Management
SOLVE:Operations Automation
SOLVE:Access Session Management
SOLVE:FTS
Issue/Introduction
It is possible that, during the operations of NetMaster for File Transfer interfacing with Connect:Direct, recurring messages
IEC130I DMMSGFIL DD STATEMENT MISSING
and
N28502 OPEN FAILED FOR VSAM ACB, CODE=X'80', DD=DMMSGFIL
will occur.
IEC130I DMMSGFIL DD STATEMENT MISSING
and
N28502 OPEN FAILED FOR VSAM ACB, CODE=X'80', DD=DMMSGFIL
will occur.
Why, during the operations of NetMaster for File Transfer interfacing with Connect:Direct, recurring messages
IEC130I DMMSGFIL DD STATEMENT MISSING and
N28502 OPEN FAILED FOR VSAM ACB, CODE=X'80', DD=DMMSGFIL can occur?
Environment
Netmaster File Transfer Management: all releases
Resolution
To remove these messages (on the fly):
Allocate it dynamically. From CMD, issue:
SUB BSYS ALLOC DD=DMMSGFIL DSN=dsname DISP=SHR
Note: Look in C:D proc the DSNAME of DMMSGFIL and use it in dsname.
To remove these messages (from the next NetMaster run):
Specify it on RUNSYSIN of NetMaster proc:
DD=DMMSGFIL,DISP=SHR,DSN=dsname
Note: Look in C:D proc the DSNAME of DMMSGFIL and use it in dsname.
Additional Information
A system can go many years without seeing the error messages for DMMSGFIL.
The DMMSGFIL contains messages and descriptions from C:D.
NFT has specific locations in the code where that file is read.
There are many causes for file transfer failure, and only specific types of failures require a C:D message; others are not C:D specific so MVS or Netmaster messages are accessed to supply the information.
If this is the first time these messageas are appearing on an established region, it is entirely possible that a file transfer (it only takes one) just now failed in such a way that Netmaster gets a failed EVENT that contains a MESSAGEID from C:D. In order to interpret that message, Netmaster makes a call to DMMSGFIL to retrieve the error message associated with that specific FAILED File Transfer.
Other places that may call DMMSGFIL include when a user does a HELP request (PF1) on the C:D message either in the NCLLOG, the Command Entry screen (CMD) or from the web interface.
In short, the cause for the messages is simply a file transfer failing with an error message that is triggering the product to READ the DMMSGFIL, and that file is not accessible to Netmaster.
The DMMSGFIL contains messages and descriptions from C:D.
NFT has specific locations in the code where that file is read.
There are many causes for file transfer failure, and only specific types of failures require a C:D message; others are not C:D specific so MVS or Netmaster messages are accessed to supply the information.
If this is the first time these messageas are appearing on an established region, it is entirely possible that a file transfer (it only takes one) just now failed in such a way that Netmaster gets a failed EVENT that contains a MESSAGEID from C:D. In order to interpret that message, Netmaster makes a call to DMMSGFIL to retrieve the error message associated with that specific FAILED File Transfer.
Other places that may call DMMSGFIL include when a user does a HELP request (PF1) on the C:D message either in the NCLLOG, the Command Entry screen (CMD) or from the web interface.
In short, the cause for the messages is simply a file transfer failing with an error message that is triggering the product to READ the DMMSGFIL, and that file is not accessible to Netmaster.
Feedback
Yes
No
Powered by
