DSNA669I   csect-name THE SUBSYSTEM PARAMETERS WERE NOT MODIFIED. REASON CODE=reason-code. additional-info

A user requested a change to the value of at least one DB2® subsystem parameter by using the SYSPROC.ADMIN_UPDATE_SYSPARM stored procedure. However, the subsystem parameters were not modified for the indicated reason.

Message DSNA669I is returned in the result table of the SYSPROC.ADMIN_UPDATE_SYSPARM stored procedure, unless the reason-code value is 01, 04, 05, 06, or 07. In these special cases, DSNA669I is displayed in the WLM job log.

csect-name

The name of the control section that issued the message.

reason-code

A numeric value that indicates the reason for the failure. reason-code can be one of the following values:

01

A REXX programming violation occurred.

02

The created global temporary table SYSIBM.SYSPARM_SETTINGS does not exist.

03

The user does not have the authority to use the created global temporary table SYSIBM.SYSPARM_SETTINGS.

04

The created global temporary table SYSIBM.UPDSYSPARM_MSG does not exist.

05

The user does not have authority to use the created global temporary table SYSIBM.UPDSYSPARM_MSG.

06

The DSNREXX package was not found.

07

DB2 cannot access a DSNREXX environment. DB2 REXX Language Support is not available.

08

All libraries in the WLM STEPLIB concatenation are APF-authorized.

09

An error occurred when validating an input parameter for the stored procedure.

10

The WLM startup procedure is missing the ZPMDFLTS DD statement.

11

A data set that is required by the stored procedure is not available for use.

12

A validation error occurred for input table SYSIBM.SYSPARM_SETTINGS for one of the following reasons:

• The table is empty.
• The table has a duplicate ROWNUM value.
• The table has a negative ROWNUM value.
• A macro name is invalid.
• A parameter is invalid.

13

An SQL error occurred when retrieving new subsystem parameter values from the input table SYSIBM.SYSPARM_SETTINGS.

14

The specified source_library parameter for the ADMIN_UPDATE_SYSPARM stored procedure is not a partitioned data set (PDS) or a partitioned data set extended (PDSE).

15

The record format (RECFM) of the specified source_library parameter for the ADMIN_UPDATE_SYSPARM stored procedure is not F or FB.

16

The record length (LRECL) of the specified source_library parameter for the ADMIN_UPDATE_SYSPARM stored procedure is not 80.

17

The ZPMDFLTS DD statement in the WLM startup procedure points to a data set that contains a SRCLIB_NAME library data set. That SRCLIB_NAME data set is not a partitioned data set (PDS) or a partitioned data set extended (PDSE).

18

The ZPMDFLTS DD statement in the WLM startup procedure points to a data set that contains a SRCLIB_NAME library data set. The record format (RECFM) of that SRCLIB_NAME data set is not F or FB.

19

The ZPMDFLTS DD statement in the WLM startup procedure points to a data set that contains a SRCLIB_NAME library data set. The record length (LRECL) of that SRCLIB_NAME data set is not 80.

20

The backup of the member that the stored procedure is to replace did not complete successfully. The member was to be replaced with the new JCL to assemble and link-edit the new subsystem parameters load module. The failure occurred for one of the following reasons:

• A backup already exists.
• An I/O error occurred.

21

One of the following errors occurred when retrieving the current values of the subsystem parameters:

• The SYSPROC.ADMIN_INFO_SYSPARM stored procedure did not complete successfully. Either the return code was greater than 0 or the SQL code was not +466, as expected.
• An SQL error occurred when processing the result set from the SYSPROC.ADMIN_INFO_SYSPARM stored procedure.

22

The required program ASMA90 was not found.

23

The required program HEWL (which executes the linkage editor) was not found.

24

The process of assembling the subsystem parameter macros did not complete successfully. The return code was greater than 0.

25

The backup of the subsystem parameters load module that is being replaced did not complete successfully for one of the following reasons:

• The backup already exists.
• A SYSDSN error occurred for a backup member.
• The linkage editor failed to make a backup copy.

26

The process of link-editing the subsystem parameters load module did not complete successfully. The return code was greater than 4.

27

The SET SYSPARM command with the LOAD option did not complete successfully for one of the following reasons:

• The SYSPROC.ADMIN_COMMAND_DB2 stored procedure did not complete successfully. Either an IFI error occurred, the return code was greater than 0, or the SQL code was not +466, as expected.
• The SET SYSPARM command returned messages that indicate that the command was not successful.

28

The result of the SET SYSPARM command with the LOAD option is unknown. An SQL error occurred when processing the result set of the ADMIN_COMMAND_DB2 stored procedure.

32

An I/O error occurred when accessing assembler and link-edit files.

33

The JCL to assemble and link-edit the new subsystem parameters load module was not saved for one of the following reasons:

• A data set allocation error occurred.
• A data set I/O error occurred.

34

The SYSPROC.ADMIN_UPDATE_SYSPARM stored procedure could not retrieve the subsystem name of the connected DB2 subsystem.

35

The SYSPROC.ADMIN_UPDATE_SYSPARM stored procedure could not retrieve the subsystem name and command prefix of the DB2 subsystem whose subsystem parameters are to be modified. This situation occurred for one of the following reasons:

• The SYSPROC.ADMIN_COMMAND_DB2 stored procedure did not complete successfully. Either an IFI error occurred, the return code was greater than 0, or the SQL code was not +466, as expected.
• An SQL error occurred when processing the result set from the ADMIN_COMMAND_DB2 stored procedure.
• The version of DB2 is not supported.

additional-info

Additional descriptive text or another message that explains the reason that the specified action failed.

Although additional-info is part of message DSNA669I, it is not returned in the same result set row. additional-info is returned in a separate row after DSNA669I. The exception is if the reason-code value is 01, 04, 05, 06, or 07. In these special cases, DSNA669I and the additional text are displayed in the WLM job log.