| |
Results |
|
Need to reinstate DB2 ATTACH\DETACH MODIFY command against STC.
|
What is need is for the following commands to be reinstated: /F cmnstc,CMN,DETACH,DB2 /F cmnstc, CMN , ATTACH , DB2
|
|
|
|
ERO 21 job not created for DB2 packages when attached to a release
|
ERO 21 job not created for DB2 packages when attached to a release
|
|
|
|
"CMN8725I - Save staging versions is not installed."
|
Performed command F SERx, CMN ,DETACH, DB2 and F SERx, CMN , ATTACH , DB2 to reconnect the impact analysis table. After the reconnection, if the VC command is entered for a component in the Active status, the following message is displayed:
|
|
|
|
Two different messages in CMN_453I Warning
|
With version 5.5.0, ChangeMan is issuing two different messages into the system log under the same CMN_453I message number. 1) When the task comes up and DB2 is attached , it issues "CMNY453I CMNDB2CA DB2 CAF Connect OK, ID=DD0G DB2 VRM=710"
|
|
|
|
Attaching dependencies to targets fails when drag and dropping in files.
|
On UNIX main server with an Oracle (or DB2 ) database, attaching dependencies to targets fails when drag and dropping in files.
|
|
|
|
DB2 threads not being freed up
|
However after the abend, the thread is not freed up. Issuing a modify DETACH and ATTACH to DB2 also does not free then up. The only ways to free them up is to re-cycle Change Man, or have the DBA issue a Disconnect command.
|
|
|
|
DB2 subsystem id for I/A changed without task being recycled.
|
Inadvertently the DB2 subsystem information was changed in admin. After a few hours, audits started to fail, and they found the change in admin. The DB2 subsystem information was corrected, but any attempt to DETACH/ ATTACH to DB2 attempted to connect to the incorrect subsystem.
|
|
|
|
Getting -501s for DB2 requests. Default DB2 is dynamically switching to the value in col 64 of global record 1.
|
Customer reported that they started getting -501s for DB2 requests, and could not identify why. When they DETACHed and ATTACHed DB2 , the DB2 subsystem had dynamically changed to the value defined in COL 64 of global record 1.
|
|
|
|
DA not formatting DB2 info for IMS DL/I batch jobs
|
** ** Two types of IMS batch attachment to DB2 are in use here: 1. DL/I jobs using IMS program DSNMTV01.
|
|
|
|
5.5.0 Tasks Shutting Themselves Down Immediately After Startup
|
In this customer's case they issue a DB2 attach command when they find a CMN _453I message. (This message used to mean DB2 was down, but now is also the message number for a successful connect - see DEF74338) This may be the command in the buffer that SERVER assumes is STOP.
|
|
|
