On Thu, 29 May 2008 05:43:29 -0500, Magen Margalit <[EMAIL PROTECTED]> wrote: >... >We are trying to migrate out CICS TOR from cross domain to VTAM GR. >...
Right off the bat, I'm confused. I understand going from a non-GR to a GR configuration, but sessions that had been cross-domain are still going to be cross-domain. >... >We have followed following procedure: >1. Shutting down TOR >2. Make definition chages in order that current applid will be VTAM GR id >3. vtam ACT to the new TOR applid. >4. vtam INACT (force) to the old TOR applid. >5. Restart TOR. > >We have encountered the following situation: >D net to the old TOR appid shows the the cross domain is still there >... "The cross domain is still there"??? A hard-coded CDRSC defintion? A dynamic CDRSC definition? A cross-domain session? I'm not sure what you are sayig here. >... >and some terminals are in POLUIO status under it. ... I think the POLUIO status relates strictly to the SSCP-LU session - VTAM has sent a USS message and is waiting for a response. I've seen this only with SLUs under real PUs, but maybe VTAM does some special USS handling in GR configurations. I think we need Chris Mason to chime in about now. >... >Other terminal's seemed to be working via the VTAM GR. >... I don't understand "working via the VTAM GR". Do you mean that they succeeded when logging onto the GR name? A Generic Resource is just a way of associating one "virtual" APPLid with a number of real APPLids (with a lot of coding behind that "just"). BTW, I assume you have multiple TORs you are trying to put "under" a GR name. Yes? If not, what are you trying to achieve with a Generic Resource configuration? >... >We brouht down the TOR again and used INACT+FORCE+DELETE >and the cross domain appl was still there. >... "Cross domain appl"? A cross-domain resource is the local representation of an LU in another domain. It may be an appl in its own domain but it's a CDRSC in the local domain. Are you saying the the CDRSC was still active? That's normal. If it's a hard-coded CDRSC it will stay forever. If it's dynamic CDRSC it will eventually be delated based on some internal VTAM timer. > >Questions: >1. It seems that terminals tring to conect after the TOR was up > worked vis the VTAM GR and others were stucked under the > old cross domain definition... I guess I still don't understand the configuration. Did you take what had been a regular TOR APPLid, change it to a GR name and change one or more TOR APPLids to new names under the GR name? The sessions that are hung were pending when you changed your config? If so, their problem probably relates as much to the old config as to the new one. If not, could you explain it again? >... >2. On the D net command, fields: Active Sessions was 0000 and > SESSION REQUESTS was > 0000 can this be the reason? What did you display? Let's hope Chris Mason takes interest in this. He's the VTAM expert around here. Pat O'Keefe ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
