View previous topic :: View next topic
|
Author |
Message |
santasudhar
New User
Joined: 12 Jun 2009 Posts: 2 Location: Chennai
|
|
|
|
Hi,
I have 2 IMS screens, say screen A and Screen B.
we can traverse from A to B using an PFkey.
USER 1 is already in SCREEN B and entered some values required in that screen. When the USER 2 traverse to SCREEN B from SCREEN A, the data entered by the USER 1 gets automatically populated for USER 2.
This does not happen often, but when many people (say more than 5) try to access the SCREENS at the same time.
I am not getting a clue much on this, and i am a bit new to IMS DC as well. Please guide me |
|
Back to top |
|
|
Sandy Zimmer
Active Member
Joined: 13 Jun 2007 Posts: 826 Location: Wilmington, DE
|
|
|
|
Transactional IMS does not carry it's own work area. Your program is "reusable". Many users will be accessing the same version of the program. Each time you "communicate", you need to repopulate your work areas. I always used fields hidden on my screen. |
|
Back to top |
|
|
Kjeld
Active User
Joined: 15 Dec 2009 Posts: 365 Location: Denmark
|
|
|
|
Is the PFkey programmed as scrollkey in the MFS screen definitions, or is the PFkey putting another input message to your MPP?
If the first is true, both screen A and screen B should always be filled in when you place them on the IOPCB. |
|
Back to top |
|
|
Sandy Zimmer
Active Member
Joined: 13 Jun 2007 Posts: 826 Location: Wilmington, DE
|
|
|
|
It obviously is used to invoke a message. Once more, transactional IMS programs do NOT carry their own work areas unlike CICS. The program executing in the region is being shared by several users. If you are the only user using that program in that region, then you may just get your information - if multiple people are using it, you have no guarantees. |
|
Back to top |
|
|
Sandy Zimmer
Active Member
Joined: 13 Jun 2007 Posts: 826 Location: Wilmington, DE
|
|
|
|
I worked on a major conversion a while ago. They couldn't find enough IMS DC programmers, so they hired some CICS consultants. They tested and tested and tested, but they tested ALONE without anyone else accessing their portion of the online DC system. Major system test came - about 2 days before critical deadline time. They had maybe 50 people online using the same function at the same time. Guess what? |
|
Back to top |
|
|
|