DFS3498W bbbb nnnnnnnn eeeeeeeeee....

Explanation

/MODIFY PREPARE, INITIATE OLC PHASE(PREPARE), or /MODIFY COMMIT processing detected an invalid condition in the MODBLKS or ACBGEN output. This problem or situation occurred during prepare processing, unless otherwise noted as commit processing.

In the message text:
bbbb
Block type, if applicable DMB represents a DMB in ACBLIB. DDIR represents a database in MODBLKS. PSB represents a PSB in ACBLIB. SMB represents a transaction in MODBLKS.
nnnnnnnn
The name of the block, if applicable.
eeeeeeeeee....
The problem or situation encountered, which might be one of the following:
ALREADY DEFINED AS PARTITION CHANGE
Issued when a database defined in the MODBLKS data set is already defined as a HALDB partition. Once a database is defined as a HALDB partition to DBRC and IMS, it remains defined to IMS as a HALDB partition until you cold start IMS and cannot be changed into a MODBLKS database, even if the HALDB partition is deleted from DBRC.
ALREADY DEFINED AS DATABASE CHANGE
Issued when the online change prepare detects that a DDIR in the MODBLKS data set that is being added exists. If this situation does occur, it is probably an internal error. Online change prepare is rejected.
ALREADY DEFINED AS DATABASE COMMIT
Issued when the online change commit detects that a DDIR in the MODBLKS data set that is being added exists. If this situation does occur, it is probably an internal error. Online change commit proceeds in spite of this error. Once a database is defined as a HALDB partition to DBRC and IMS, it remains defined to IMS as a HALDB partition until you cold start IMS and cannot be changed into a MODBLKS database, even if the HALDB partition is deleted from DBRC.
ALREADY DEFINED AS PARTITION COMMIT
Issued when the online change commit detects that a member in the MODBLKS data set is defined using the same name as an existing HALDB partition added since the prepare phase. The HALDB partition definition prevails. Online change commit proceeds in spite of this error. Subsequent PREPARE commands fail with DFS3498W DDIR dbname ALREADY DEFINED AS PARTITION CHANGE as long as the database remains in the inactive MODBLKS data set.
ALREADY DEFINED AS TRANSACTION
This string is issued when a /MODIFY COMMIT or INITIATE OLC PHASE(COMMIT) detects that a transaction being added by an online change was added as a CPIC transaction by the same name since prepare. Online Change proceeds in spite of this error. The transaction remains a CPIC transaction. If you prefer the MODBLKS definition, define the transaction again in the inactive MODBLKS dataset and do another online change.
NOT IN ACTIVE LIBRARY
Issued when /MODIFY PREPARE or INITIATE OLC PHASE(PREPARE) is specified with the BLDL option, to cause information message DFS3498I to be issued for each PSB or DMB not found in the inactive ACBLIB. This message does not affect the success of the command.
NOT IN INACTIVE LIBRARY
Issued when /MODIFY PREPARE or INITIATE OLC PHASE(PREPARE) is specified with the BLDL option, to cause information message DFS3498W to be issued for each PSB or DMB not found in the active ACBLIB. This message does not affect the success of the command.
PDIR NAME IS INVALID
Issued when a transaction being added or changed defines an application program name that does not exist.
SID NUMBER IS INVALID
Issued when a transaction being added or changed defines a SYSID that is larger than the maximum SYSID that was used at IMS cold start.
SNO - COMPARE
Issued when the online change compare function detects that a DMB or PSB in ACBLIB is being changed, but cannot find the associated local control block (DDIR or PDIR). This error should not occur (SNO), since the local control block did exist when the BLDL list was built.
SNO - INSERT CHANGE
Issued when online change tries to insert a changed DMB or PSB into the change list, but cannot find the associated local control block (DDIR or PDIR). This error should not occur (SNO) and usually indicates that the wrong MODBLKS data set is being used. It might also indicate an internal error.
SNO - INSERT DELETE
Issued when online change tries to insert a deleted DMB or PSB into the delete list, but cannot find the associated local control block (DDIR or PDIR). This error should not occur (SNO) and usually indicates that the wrong MODBLKS data set is being used. It might also indicate an internal error.
SYSID CHNG IS INVALID
Issued when a transaction is being changed from local to remote and at least one other type of change to the transaction or application program is being attempted as well.
UNSUPPORTED MSDB ADDITION
Issued when online change attempts to add, change, or delete an MSDB database in MODBLKS or DMB in ACBLIB, which is not supported.
UNSUPPORTED MSDB CHANGE
Issued when online change attempts to change an MSDB database in MODBLKS or DMB in ACBLIB, which is not supported.
UNSUPPORTED MSDB DELETION
Issued when online change attempts to delete an MSDB database from MODBLKS or DMB from ACBLIB, which is not supported.

System action

For a /MODIFY PREPARE or INITIATE OLC PHASE(PREPARE) command, the command is terminated. For a /MODIFY COMMIT command, the online change commit succeeds, except for the specified database. The database remains a HALDB partition.

Programmer response

Correct the problem, run the MODBLKS GEN or ACBGEN again, run the Online Change utility, and retry online change.

For a /MODIFY COMMIT command that failed with DFS3498W DDIR dbname ALREADY EXISTS AS PARTITION COMMIT, perform an online change to remove this database definition from your MODBLKS gen. Otherwise, each subsequent attempt to do an online change will fail on the /MODIFY PREPARE command with DFS3498W DDIR dbname ALREADY EXISTS AS PARTITION CHANGE. Also, the database reverts to a non-HALDB database at the next IMS cold start.

For the warning SID NUMBER IS INVALID, generate a transaction with a SYSID that does not exceed the maximum SYSID. Or, cold start IMS with the MODBLKS data set that contains the transaction defined with the highest SYSID.

Module

DFSCPDD0, DFSRMDD0, DFSRMDM0, DFSRMPS0, DFSRMSM0