mensingdonn |
Make sure you have the IMS RESLIB before SDSNLOAD in the steplib.
mensingdonn |
IMS and DB2 share DSNHLI. If you are using Cobol and DYNAM you need to have the IMS RESLIB before the DB2 SDSNLOAD in your steplib. Also enter the command ‘/ssr -dis thread(*)’ in IMS to make sure IMS is conected to DB2.
mensingdonn |
IMS and DB2 share DSNHLI. If you are using Cobol and DYNAM you need to have the IMS RESLIB before the DB2 SDSNLOAD in your steplib. Also enter the command ‘/ssr -dis thread(*)’ in IMS to make sure IMS is conected to DB2.
mensingdonn |
Is this a IMS/TM or DBCTL regeion? In your IMS proclib you should have a member that has the connection information to DB2 to tell you what the CRC is, most site use the IMS subsystem id followed by the DB2 subsystem id.
If your IMS id is IMST and your DB2 id is DB2T in proclib you should have a member IMSTDB2T that should have your CRC in it.
You should not have to shutdown the IMS region to run batch tests, just DBR the data base in IMS. If the batch job runs and uses DBRC, has checkpiont restart and all the things that are standard practices you should just be able to change from DLI to BMP in the parm.
DB2, UDB for mainframe, z/OS, OS/390, Instant Messaging
Application developers have nearly completed a conversion from IMS to DB2. They have used BMP to leave their test subsystems available to online tranactions. One day BMP users of BMP failed with U3042. This only occured for BMP users testing with IMS & DB2 databases. I am investigating the issue, without much IMS support experience. In addition, IMS is backleveled. (a) I checked the connection between IMS and DB2 (DIS STATUS; DIS ACTIVE; DIS CCTL) and the connection looks like it is available. Since the BMP/IMS/DB2 
0
