A fix is available
APAR status
Closed as program error.
Error description
Users of DB2 Administration Tool for z/OS report that SQL jobs running WSL (Work Statement List) now fail if SSID parm to ADBTEP2 is omitted. Same job ran ok, previously. Now, SSID parm is required, but even an invalid SSID parm is accepted. . Admin User Guide indicates SSID parm is optional for SQL jobs. . Failing jobs end rc8 rc08 with error messages similar to: . ADB5008E Either the SSID() or PLAN= parameter was not provided. ADB5185E The run is ending due to errors. ADBT010W - Rollback performed due to previous error . Additional search words: cc8 cc08 msgadb5185e
Local fix
Edit job to add SSID(dbid) to ADBTEP2 parms, like: RUN PROGRAM(ADBTEP2) PLAN(ADB72MPE) LIB('DMTOOL.ADB72MPE.SADBLLIB') PARMS('/WORKLIST(PM73275) SSID(XXXX) RESTART(YES) ')
Problem summary
**************************************************************** * USERS AFFECTED: Users of the DB2 Administration Tool for * * z/OS who use the Batch Restart program * * ADBTEP2. * **************************************************************** * PROBLEM DESCRIPTION: The DB2 Administration Tool for z/OS * * Batch Restart program ADBTEP2 running * * SQL in Work Statement List (WSL) * * fails if the SSID parameter provided * * is omitted. It seems the SSID parameter * * is required, however, the DB2 * * Administration Tool User's Guide * * Version 10.1 indicates the SSID is * * optional for running SQL jobs. * * * * The job ends with a RC8 and error * * messages: * * * * ADB5008E Either the SSID() or PLAN= * * parameter was not provided. * * * * ADB5185E The run is ending due to * * errors. * * * * ADBT010W - Rollback performed due * * to previous error * * * * Additionally, an invalid SSID * * parameter is accepted by ADBTEP2 * * as if a correct value had been * * given. * **************************************************************** * RECOMMENDATION: * **************************************************************** The DB2 Administration Tool for z/OS Batch Restart program ADBTEP2 running SQL in WSL fails with error ADB5008E if SSID parameter passed to ADBTEP2 is omitted. However, the DB2 Administration Tool Version 10.1 User's Guide indicates the SSID is optional for running SQL jobs. Additionally, an invalid SSID parameter is accepted by ADBTEP2.
Problem conclusion
The DB2 Administration Tool Version 10.1 User's Guide was modified to indicate the SSID parameter is required for program ADBTEP2. The program was also modified to validate the SSID parameter based on the following: (1) If SSID parameter is not provided, ADBTEP2 will issue an error message ADB5008E and stop processing. (2) If SSID parameter is provided, ADBTEP2 will validate the SSID using DB2 stored procedure SYSPROC.ADMIN_INFO_SSID. (3) If an error is produced for call SYSPROC.ADMIN_INFO_SSID statement such as the stored procedure is not available, ADBTEP2 will issue a warning message ADB5254W but continue processing. (4) If the stored procedure returns an error, ADBTEP2 will issue a warning message ADB5255W but continue processing. (5) If the stored procedure returns successfully and SSID does not match the returned name of the connected DB2 subsystem, ADBTEP2 will issue an error message ADB5256E to indicate an unrecognized SSID parameter was provided. (6) If the stored procedure returns successfully and SSID matches the returned name of the connected DB2 subsystem, ADBTEP2 will continue processing without any messages issued. Referring to below messages: ADB5008E Either the SSID() or PLAN= parameter was not provided. ADB5254W The stored procedure SYSPROC.ADMIN_INFO_SSID is not available for validating the SSID parameter. The program skips the validation. ADB5255W The call to the stored procedure SYSPROC.ADMIN_INFO_SSID did not complete successfully. The program skips the validtion. ADB5256E The SSID parameter passed to the program is not recognized. The parameter does not match the name of the connected DB2 subsystem returned from the stored procedure SYSPROC.ADMIN_INFO_SSID. The SSID parameter passed to Batch Restart program ADBTEP2 is used for running non-SQL commands or functions. Currently, it is a required parameter for ADBTEP2 to avoid any further errors. The description for SSID parameter under the section 'Parameters passed to ADBTEP2' in the DB2 Administration Tool Version 10.1 User's Guide need to be changed as below. Before: SSID(name) A subsystem or group attachment name to be used for running non-SQL commands or functions. This name should be the same as that used in the DSN SYSTEM(xxxx), which is used ahead of the RUN command that invokes ADBTEP2. This parameter is mandatory if any non-SQL DB2 function is included in the input stream (for example, a DSN command). Change to: SSID(name) A subsystem or group attachment name to be used for running non-SQL commands or functions. This name should be the same as that used in the DSN SYSTEM(xxxx), which is used ahead of the RUN command that invokes ADBTEP2. Additionally, the following messages are added to the DB2 Administration Tool Version 10.1 User's Guide: ADB5254W The stored procedure SYSPROC.ADMIN_INFO_SSID is not available for validating the SSID parameter. The program skips the validation. Explanation: The SSID parameter passed to the program could not be validated because the attempt to call the stored procedure SYSPROC.ADMIN_INFO_SSID failed. System action: Processing continues. User response: None. ADB5255W The call to the stored procedure SYSPROC.ADMIN_INFO_SSID did not complete successfully. The program skips the validation. Explanation: The SSID parameter passed to the program could not be validated because the return code from the stored procedure SYSPROC.ADMIN_INFO_SSID is not zero. System action: Processing continues. User response: None. ADB5256E The SSID parameter passed to the program is not recognized. The parameter does not match the name of the connected DB2 subsystem returned from the stored procedure SYSPROC.ADMIN_INFO_SSID. Explanation: The SSID parameter passed to the program must be the same name of the connected DB2 subsystem returned from DB2 stored procedure SYSPROC.ADMIN_INFO_SSID. System action: Processing stops. User response: Specify the correct value.
Temporary fix
Comments
ž**** PE12/06/27 PTF IN ERROR. SEE APAR PM67776 FOR DESCRIPTION
APAR Information
APAR number
PM56278
Reported component name
DB2 ADMIN TOOL
Reported component ID
568851500
Reported release
A10
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-01-18
Closed date
2012-05-23
Last modified date
2012-09-25
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK78985
Modules/Macros
ADBTEP2 ADB5000 ADB7000
Fix information
Fixed component name
DB2 ADMIN TOOL
Fixed component ID
568851500
Applicable component levels
RA10 PSY UK78985
UP12/05/30 P F205
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSCVQTD","label":"IBM Db2 Administration Tool for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
25 September 2012