Product Documentation
Abstract
Updates that apply to DB2® Bind Manager for z/OS®, Version 2.4 User's Guide (SC19-2751-04)
Content
Update 5
Date of change: March 26, 2014
Topic: Running ISPF mode
Change description: The sample changed in Figure 5: CLIST BNDC002 code modification.
Download the PDF for the contents of the revised sample:
BMUG-V24_Running_ISPF_Mode.pdfUpdate 4
Date of change: September 26, 2011
Topic: Bind Avoidance
Change description: The following information is updated for APAR PM31485:
bndugc43_bindavoidance.pdfUpdate 3
Date of change: September 26, 2011
Topic: DB2 Bind Manager messages and codes
Change description: The following messages were added for APAR PM31485:
BND3201I EXECUTING BNDAVB4 maintenance-level
Explanation: The BNDAVB4 program is running. The alphanumeric characters represent the maintenance level of the module.
Programmer response: No action is required. If you report a problem, include the maintenance level.
Module: BNDAVB4
BND3235E DBRM PROCESS FAILURE ddname DDNAME MISSING
Explanation: The JCL does not contain one or more of the following DD statements:
- DBRMIN DD
- SOURCIN DD
- SOURCEOT DD
Module: BNDAVB1
Update 2
Date of change: April 15, 2011
Topic: Troubleshooting
Change description: The following messages have been added in APAR PM34664:
BND3100S Module module_name could not be loaded, reason=diagnostic_code
Explanation: A required load module could not be accessed. In the message text, module_name is the name of the missing module.
Programmer response: Modify your system or TSO session configuration so that the required module is
available via STEPLIB, link list, or another method.
Module: BNDA075
BND3101E SYSUT1 must be allocated in the BNDC002
Explanation: The SYSUT1 work file has not been allocated.
Programmer response: Verify that you are using the most current version of CLIST BNDC002 and that the CLIST has not been incorrectly modified.
Module: BNDA075
BND3102E Enter one of the listed options
Explanation: An invalid option was specified.
Programmer response: Specify a valid option on the panel.
Module: BNDA075
BND3103S SQL ERROR type_of_SQL_request, type_of_SQL_request, sqlcode=code_number
Explanation: An SQL statement failed unexpectedly.
Programmer response: Record the information in the message text, and contact IBM Software Support.
Module: BNDA075
BND3104E DBRM generation failed, reason=code_number
Explanation: DB2 Bind Manager could not retrieve DBRM information from the catalog. The diagnostic return code indicates the failing code path.
Programmer response: Record the information in the message text, and contact IBM Software Support.
Module: BNDA075
BND3105E DBRM generation failed, reason=code_number
Explanation: DB2 Bind Manager could not retrieve DBRM information from the catalog. The diagnostic return code indicates the failing code path.
Programmer response: Record the information in the message text, and contact IBM Software Support.
Module: BNDA075
BND3106S Unable to connect to subsystem subsystem_ID, return code=code_number, reason=code_number
Explanation: DB2 Bind Manager could not access the specified DB2 subsystem. The return code and reason code are from the call attachment facility.
Programmer response: Ensure that the subsystem name is correct and that the subsystem is running and available. If the problem persists, analyze the the return and reason codes from the call attachment facility to determine why the subsystem is inaccessible. For more information, see the DB2 Application Programming and SQL Guide in the IBM Product Information Center.
Module: BNDA075
BND3107I There are no catalog entries matching your criteria
Explanation: The specified plan or package does not exist in the subsystem catalog.
Programmer response: Ensure that the subsystem name and requested plan or package names are specified correctly and that the plan or package exists in the indicated subsystem.
Module: BNDA075
BND3108E Only one entry may be processed at a time
Explanation: Multiple line commands were entered on a panel that can process only one entry at a time.
Programmer response: Select only one line command, and press Enter.
Module: BNDA075
BND3109E Data_set_name could not be allocated. Reason: code_number
Explanation: The specified data set could not be allocated. The return code was issued by TSO ALLOCATE.
Programmer response: Ensure that the data set name, is spelled correctly, exists, and is not in use by another user.
Module: BNDA075
BND3110I DBRM DBRM_name stored in data_set_name
Explanation: The requested DBRM was generated and saved. The data set name is the name of the DBRMLIB where the DBRM was saved.
Programmer response: No action is required.
Module: BNDA075
BND3111E DBRM Data_set_name could not be allocated. Reason: code_number
Explanation: The specified data set could not be allocated. The return code was issued by TSO
ALLOCATE.
Programmer response: Ensure that the data set name is spelled correctly, exists, and is not in use by another user.
Module: BNDA075
BND3112E DBRM Invalid DBRM library -- invalid_attribute_name
Explanation: A valid DBRMLIB is a partitioned data set with fixed-length 80-byte records. The specified data set lacks one or more of the required attributes. Possible values for invalid_attribute_name are “not
partitioned,” “LRECL”, and “RECFM.”
Programmer response: Specify a valid DBRM library.
Module: BNDA075
BND3112E DBRM Invalid DBRM library -- invalid_attribute_name
Explanation: A valid DBRMLIB is a partitioned data set with fixed-length 80-byte records. The specified data set lacks one or more of the required attributes. Possible values for invalid_attribute_name are “not
partitioned,” “LRECL”, and “RECFM.”
Programmer response: Specify a valid DBRM library.
Module: BNDA075
BND3114S Unable to connect to subsystem subsystem_ID, return code=code_number, reason code=code_number
Explanation: DB2 Bind Manager could not access the specified DB2 subsystem. The return code and reason codes are from the call attachment facility.
Programmer response: Ensure that the subsystem name is correct and that the subsystem is running and available. If the problem persists, analyze the return codes and reason codes from the call attachment facility in the DB2 Application Programming and SQL Guide to determine why the subsystem is inaccessible.
Module: BNDA075
BND3115S Line_command is not a valid line command; 'S' and '/' are the only acceptable entries
Explanation: The specified line command is not valid.
Programmer response: Specify a valid line command. Valid line commands are S and /.
Module: BNDA075
BND3117S Unable to disconnect from subsystem subsystem_name, return code=code_number, reason=code_number
Explanation: DB2 Bind Manager could not disconnect from the specified DB2 subsystem. The return code and reason code are from the call attachment facility.
Programmer response: Analyze the call attachment return and reason codes in the DB2 Application
Programming and SQL Guide to determine why DB2 Bind Manager could not disconnect from the DB2
subsystem.
Module: BNDA075
BND3118S value_name value_name failed, RC=code_number
Explanation: An ISPF service failed unexpectedly. In the message text, the value names are strings that
identify the type of ISPF service request. The code number is the condition code that is returned by ISPF.
Programmer response: Capture a screen shot that contains the entire message, and contact IBM Software Support.
Module: BNDA075
BND3119E Logic error in BNDA075 message routine, symptom=number
Explanation: This message should not be issued in normal operation. It indicates that a message number that was generated internally by DB2 Bind Manager was invalid.
Programmer response: Save all of the output, and contact IBM Software Support.
Module: BNDA075
Update 2
Date of change: March 10, 2011
Topic: Troubleshooting
Change description: The following messages have been added in APAR PM31010:
BND2917I SYSPACKAGE ENTRY=dbrmname WITH VERSION version NOT FOUND
Explanation: The new DBRM specified a version that did not exist in SYSIBM.SYSPACKAGE. The bind must be processed.
Programmer response: No action is required.
Module: BNDAVB3
BND2918I SYSPACKAGE ENTRY=dbrmname WITH VERSION version HAD CONTOKEN contoken_value AND MATCHES NEW DBRM
Explanation: The new DBRM specified a version that exists in SYSIBM.SYSPACKAGE, and the contoken value matches. The bind will not be processed.
Programmer response: No action is required.
Module: BNDAVB3
BND2919I SYSPACKAGE ENTRY=dbrm_name WITH VERSION version HAD CONTOKE contoken_value AND DOES NOT MATCH NEW DBRM
Explanation: The new DBRM specified a version that exists in SYSIBM.SYSPACKAGE, and the CONTOKEN value does not match. The bind must be processed.
Programmer response: No action is required.
Module: BNDAVB36
Update 1
Date of change: March 4, 2011
Topic: Troubleshooting
Change description: The following messages have been added in APAR PM26654 :
BND2461E Invalid command (RESTART may not be combined with other commands)
Explanation: When the RESTART command is used, it must be the only specified command. It may not be used in the same run with any other commands.
Programmer response: If the job is intended to be the first job of a series, remove the RESTART command, specify the command and options, and submit. If the job is not the first job in a series, remove the other commands, add the RESTART command, and submit until the job has completed processing.
Module: BNDA036
BND2465S Premature end of data in checkpoint file
Explanation: The checkpoint file has been overwritten or corrupted.
Programmer response: Rerun the job series, starting with the initial job.
Module: BNDA036
BND2466I Run complete -- commands generated
Explanation: After the final job of a Checkpoint/Restart series, this message indicates that all requested packages and load modules have been checked and FREE commands, if any, have been generated.
Programmer response: No action is required.
Module: BNDA036
BND2467I Job series is complete -- RESTART is ignored
Explanation: The final RESTART job of the series is complete, and any FREE commands have been issued.
Programmer response: No action is required.
Module: BNDA036
Publication Number
SC19-2751-03
Copyright Date
2000, 2010
Related Information
[{"Product":{"code":"SSCVQTD","label":"IBM Db2 Administration Tool for z\/OS"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"DB2 Bind Manager","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"2.4.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Was this topic helpful?
Document Information
Modified date:
11 February 2021
UID
swg27018082