Ansicht
Dokumentation

SQL7909 - &1 was created, changed, or dropped, but object not modified. ( OS/400 )

Vendor Master (General Section)   ROGBILLS - Synchronize billing plans  
This documentation is copyright by IBM.


Message : SQL7909
&1 was created, changed, or dropped, but object not modified.

Message Long Text :

Cause . . . . . : The routine or global variable &1 in &2 was created, changed, or dropped successfully but the object's attributes could not be saved, changed, or removed from the associated program or service program object. For a routine, the specific name is &3. If the object was just created or modified, when the *PGM or *SRVPGM object is saved and then restored, the SQL catalogs will not be updated with the new attributes for this routine. If the object was just dropped, the SQL catalogs could be incorrectly updated on a future restore of the object due to not removing the object information from the associated program or service program.
Reason code is &4. Reason codes and their meanings are:
1 -- The external program did not exist when the CREATE, ALTER, COMMENT, LABEL, or DROP statement was issued.
2 -- The external program library is QSYS.
3 -- The external program was not an ILE *PGM or *SRVPGM.
4 -- The program object for the corresponding routine or variable was in use by another job.
5 -- The SQL associated space in the program was in use by another job.
6 -- The SQL associated space in the program could not be expanded.
7 -- The external program was compiled in a release prior to V4R4M0.
8 -- The SQL associated space in the external program already contains the maximum number of routine definitions.
9 -- The external program is not in the same Independent ASP (IASP) as the routine.
Recovery . . . : Do one of the following based on the reason code:
1 -- Ensure that the external program exists when the CREATE statement is issued.
2 -- Ensure that the external program library is not QSYS.
3 -- Ensure that the external program is an ILE *PGM or *SRVPGM.
4 -- Use WRKOBJLCK to ensure that the program is available when the object is created or changed.
5 -- Ensure that the program is available when the object is created or changed.
6 -- Try recompiling the external program to rebuild the program's associated space. For a global variable, simplify the default value expression.
7 -- Recompile the external program in a more recent release.
8 -- Drop one of the routines currently defined for the external program.
9 -- Ensure the external program is in the same IASP as the procedure.

Message File : QSQLMSG
Library Message File : QSYS2924


SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   PERFORM Short Reference  
This documentation is copyright by IBM.

Length: 3281 Date: 20240425 Time: 075654     sap01-206 ( 3 ms )