Pcom v4.2 and VTAM 4r2
Rob
Pcom v4.2 connects, but no application start for any session until
the PU actived (it is already active), then the apps start.
Is this a PCOM config or VTAM config?
--
Rob
Email: R...@Spot.Demon.Co.Uk
VM/VSE WIN NT - "To Infinity & Beyond"
John S. Giltner, Jr
'no application start for any session until the PU actived ( it is
already active)'
Sessions can not start until VTAM on the mainframe see's the PU in an
active state and the LU is in a SLU ENABLED status.
If the PU is active and issuing a second active command allows LU to LU
sessions, then I would check the LU and see what its SLU status is. My
guess is that it is DISABLED. If so, then either the PU is not telling
VTAM when the LU's SLU status become ENABLED, or VTAM is not ENABLING
the SLU status when it gets the msg.
Rob
*** Connection established - SBD402 active ***
IST590I CONNECTIN ESTABLISHED FOR PU SCUBD4 ON LINE L009
vtam d net,id=l009,e
Ready;
IST097I DISPLAY ACCEPTED
IST075I NAME = L009, TYPE = LINE
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
IST087I TYPE = SWITCHED DIAL-IN , CONTROL = SDLC
IST936I ANSWER MODE = ENABLED
IST1440I USE = NCP, DEFINED RESOURCE, CANNOT BE REDEFINED
IST134I GROUP = NCPSW, MAJOR NODE = NCP0401
IST084I NETWORK NODES:
IST089I SCUBD4 TYPE = PHYSICAL UNIT , ACTIV
IST089I SBD401 TYPE = LOGICAL UNIT , ACTIV
IST089I SBD402 TYPE = LOGICAL UNIT , ACTIV
IST089I SBD403 TYPE = LOGICAL UNIT , ACTIV
IST089I SBD404 TYPE = LOGICAL UNIT , ACTIV
IST089I SBD405 TYPE = LOGICAL UNIT , ACTIV
IST089I SBD406 TYPE = LOGICAL UNIT , ACTIV
IST314I END
vtam d net,id=scubd4,e
Ready;
IST097I DISPLAY ACCEPTED
IST075I NAME = SCUBD4, TYPE = PU_T2.1
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
IST1043I CP NAME = ***NA***, CP NETID = GBSCC000, DYNAMIC LU = NO
IST136I SWITCHED SNA MAJOR NODE = VTMSW2
IST081I LINE NAME = L009, LINE GROUP = NCPSW, MAJNOD = NCP0401
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST355I LOGICAL UNITS:
IST080I SBD401 ACTIV SBD402 ACTIV SBD403 ACTIV
IST080I SBD404 ACTIV SBD405 ACTIV SBD406 ACTIV
IST314I END
vtam v net,id=sbd401,e
Ready;
IST039I VARY FAILED - CANNOT IDENTIFY COMMAND TYPE
vtam d net,id=sbd402,e
Ready;
IST097I DISPLAY ACCEPTED
IST075I NAME = GBSCC000.SBD402, TYPE = LOGICAL UNIT
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
IST977I MDLTAB=***NA*** ASLTAB=***NA***
IST861I MODETAB=M4TUMODE USSTAB=VTMUSSTR LOGTAB=***NA***
IST934I DLOGMOD=M4DYNAMS USS LANGTAB=***NA***
IST597I CAPABILITY-PLU INHIBITED,SLU DISABLED ,SESSION LIMIT 00000001
IST136I SWITCHED SNA MAJOR NODE = VTMSW2
IST081I LINE NAME = L009, LINE GROUP = NCPSW, MAJNOD = NCP0401
IST135I PHYSICAL UNIT = SCUBD4
IST082I DEVTYPE = LU , CONTROLLING LU = TUBES
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST171I ACTIVE SESSIONS = 0000000000, SESSION REQUESTS = 0000000000
IST172I NO SESSIONS EXIST
IST314I END
vtam v net,act,id=scubd4
Ready;
IST097I VARY ACCEPTED
IST093I SCUBD4 ACTIVE
vtam d net,id=scubd4,e
Ready;
IST097I DISPLAY ACCEPTED
IST075I NAME = SCUBD4, TYPE = PU_T2.1
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
IST1043I CP NAME = ***NA***, CP NETID = GBSCC000, DYNAMIC LU = NO
IST136I SWITCHED SNA MAJOR NODE = VTMSW2
IST081I LINE NAME = L009, LINE GROUP = NCPSW, MAJNOD = NCP0401
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST355I LOGICAL UNITS:
IST080I SBD401 ACTIV SBD402 ACT/S SBD403 ACTIV
IST080I SBD404 ACTIV SBD405 ACTIV SBD406 ACTIV
IST314I END
IST530I AM GBIND PENDING FROM CDRMS3 TO CDRMS1 FOR CDRMS1
IST1051I EVENT CODE = 0202
IST1062I EVENT ID = 00000003000100000001000102020F3100000004
IST314I END
John S. Giltner, Jr
When a PU is activated VTAM then sends out a ACTLU for every LU. The
response back tells VTAM what LU (PLU or SLU) capabilities it has and how
many sessions it can handle. You can run a trace to verify, but the ACTLU
response is most likely coming back and telling VTAM that this SLU is
disabled. The second act of the PU says that it is enabled, I would also
guess that if you just issued an activate for the LU it would also come back
enabled.
I would assume that this is a SNA gateway PC emulating a PU and LU's. I
would also assume that the PU part of the gateway is getting active way
before the LU are ready. Normally once the LU's are ready for sessions they
tell VTAM (actually the PU does on behalf of the LU) that it is now ready
(SLU ENABLE) for sessions.
If the SNA gateway has a pool of LU's that are dynamically connected to 3270
emulators sitting on your users PC's, this is the "normal" status. The LU is
DISABLED until a user requests a 3270 connection, then the PU will tell VTAM
to enable the LU and the session starts.
Rob wrote:
> Here is a copy from VTAM log
>
> *** Connection established - SBD402 active ***
>
>
> vtam d net,id=sbd402,e
> Ready;
> IST097I DISPLAY ACCEPTED
> IST075I NAME = GBSCC000.SBD402, TYPE = LOGICAL UNIT
> IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
> IST977I MDLTAB=***NA*** ASLTAB=***NA***
> IST861I MODETAB=M4TUMODE USSTAB=VTMUSSTR LOGTAB=***NA***
> IST934I DLOGMOD=M4DYNAMS USS LANGTAB=***NA***
> IST597I CAPABILITY-PLU INHIBITED,SLU DISABLED ,SESSION LIMIT 00000001
> IST136I SWITCHED SNA MAJOR NODE = VTMSW2
> IST081I LINE NAME = L009, LINE GROUP = NCPSW, MAJNOD = NCP0401
> IST135I PHYSICAL UNIT = SCUBD4
> IST082I DEVTYPE = LU , CONTROLLING LU = TUBES
> IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
> IST171I ACTIVE SESSIONS = 0000000000, SESSION REQUESTS = 0000000000
> IST172I NO SESSIONS EXIST
> IST314I END
> vtam v net,act,id=scubd4
>
Peter Neidhart
> When a PU is activated VTAM then sends out a ACTLU for every LU. The
> response back tells VTAM what LU (PLU or SLU) capabilities it has and how
> many sessions it can handle. You can run a trace to verify, but the ACTLU
> response is most likely coming back and telling VTAM that this SLU is
> disabled.
That depends on the actual LU status. The LU stat tells if the LU can
establish sessions.
For example, if you have a REAL 3270 terminal attached to a control
unit. the SLU is disabled
unless the terminal is switched on. then a NOTIFY is sent to SSCP. Same
happens
when you switch off the terminal. Again the PU sents a NOTIFY to SSCP
tellung
the LU is disabled.
Similar is valid with SNA server which emulates a PU. The SLU is
disabled until
a programm (PCOM ) attachs to this LU.
> The second act of the PU says that it is enabled, I would also
> guess that if you just issued an activate for the LU it would also come back
> enabled.
No, thats not true. You can ACTPU as often as you like,
that doesn't change the LU status. Note that PLU and SLU status values
are only valid if the PU ist ACTIVE.
John S. Giltner, Jr
default scope is ends up issuing a activate LU for all LU's under the PU.
Peter Neidhart wrote:
--
Regards,
John S. Giltner, Jr.
Manager Network and Customer Service
ATPCO
... Solutions for the Travel Industry
Voice 703-471-7510 X1223
Fax 703-471-1492
IBMMail USATP001
SITA/ARINC IADQTXD
Rob
VTAM 4r2 is new to me, as we are just moving from VM/SP 6 with VTAM 3r2 (Yes,
I know we are leaving abit late).
Any way a third party installed all the software. But after various chat with
Third Party and IBM. A couple of things emerged.
1) Are VTAM was a base release. No fixes. Ibm quote 'Oh, you don't want to
go live with that' unquote.
2) On of the first fixes for this was, yes you've guess, logappl not working
on switched lines
3) I have run a number of VTAM traces, PCOM was sending SLU disabled, when
about 5 seconds later send SLU enabled.
Fixes will arrive on Monday, I will let you know how I get on.
Rob
Email: R...@Spot.Demon.Co.Uk
VM/VSE WIN NT - "To Infinity & Beyond"
Rob wrote:
> Here is a copy from VTAM log
>
> *** Connection established - SBD402 active ***
>
> IST590I CONNECTIN ESTABLISHED FOR PU SCUBD4 ON LINE L009
> vtam d net,id=l009,e
> Ready;
> IST097I DISPLAY ACCEPTED
> IST075I NAME = L009, TYPE = LINE
> IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
> IST087I TYPE = SWITCHED DIAL-IN , CONTROL = SDLC
> IST936I ANSWER MODE = ENABLED
> IST1440I USE = NCP, DEFINED RESOURCE, CANNOT BE REDEFINED
> IST134I GROUP = NCPSW, MAJOR NODE = NCP0401
> IST084I NETWORK NODES:
> IST089I SCUBD4 TYPE = PHYSICAL UNIT , ACTIV
> IST089I SBD401 TYPE = LOGICAL UNIT , ACTIV
> IST089I SBD402 TYPE = LOGICAL UNIT , ACTIV
> IST089I SBD403 TYPE = LOGICAL UNIT , ACTIV
> IST089I SBD404 TYPE = LOGICAL UNIT , ACTIV
> IST089I SBD405 TYPE = LOGICAL UNIT , ACTIV
> IST089I SBD406 TYPE = LOGICAL UNIT , ACTIV
> IST314I END
> vtam d net,id=scubd4,e
> Ready;
> IST097I DISPLAY ACCEPTED
> IST075I NAME = SCUBD4, TYPE = PU_T2.1
> IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
> IST1043I CP NAME = ***NA***, CP NETID = GBSCC000, DYNAMIC LU = NO
> IST136I SWITCHED SNA MAJOR NODE = VTMSW2
> IST081I LINE NAME = L009, LINE GROUP = NCPSW, MAJNOD = NCP0401
> IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
> IST355I LOGICAL UNITS:
> IST080I SBD401 ACTIV SBD402 ACTIV SBD403 ACTIV
> IST080I SBD404 ACTIV SBD405 ACTIV SBD406 ACTIV
> IST314I END
> vtam v net,id=sbd401,e
> Ready;
> IST039I VARY FAILED - CANNOT IDENTIFY COMMAND TYPE
> vtam d net,id=sbd402,e
> Ready;
> IST097I DISPLAY ACCEPTED
> IST075I NAME = GBSCC000.SBD402, TYPE = LOGICAL UNIT
> IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
> IST977I MDLTAB=***NA*** ASLTAB=***NA***
> IST861I MODETAB=M4TUMODE USSTAB=VTMUSSTR LOGTAB=***NA***
> IST934I DLOGMOD=M4DYNAMS USS LANGTAB=***NA***
> IST597I CAPABILITY-PLU INHIBITED,SLU DISABLED ,SESSION LIMIT 00000001
> IST136I SWITCHED SNA MAJOR NODE = VTMSW2
> IST081I LINE NAME = L009, LINE GROUP = NCPSW, MAJNOD = NCP0401
> IST135I PHYSICAL UNIT = SCUBD4
> IST082I DEVTYPE = LU , CONTROLLING LU = TUBES
> IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
> IST171I ACTIVE SESSIONS = 0000000000, SESSION REQUESTS = 0000000000
> IST172I NO SESSIONS EXIST
> IST314I END
> vtam v net,act,id=scubd4
> Ready;
> IST097I VARY ACCEPTED
> IST093I SCUBD4 ACTIVE
> vtam d net,id=scubd4,e
> Ready;
> IST097I DISPLAY ACCEPTED
> IST075I NAME = SCUBD4, TYPE = PU_T2.1
> IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
> IST1043I CP NAME = ***NA***, CP NETID = GBSCC000, DYNAMIC LU = NO
> IST136I SWITCHED SNA MAJOR NODE = VTMSW2
> IST081I LINE NAME = L009, LINE GROUP = NCPSW, MAJNOD = NCP0401
> IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
> IST355I LOGICAL UNITS:
> IST080I SBD401 ACTIV SBD402 ACT/S SBD403 ACTIV
> IST080I SBD404 ACTIV SBD405 ACTIV SBD406 ACTIV
> IST314I END
> IST530I AM GBIND PENDING FROM CDRMS3 TO CDRMS1 FOR CDRMS1
> IST1051I EVENT CODE = 0202
> IST1062I EVENT ID = 00000003000100000001000102020F3100000004
> IST314I END
>
> "John S. Giltner, Jr" wrote:
>
> > I am confused by your statement.
> >
> > 'no application start for any session until the PU actived ( it is
> > already active)'
> >
> > Sessions can not start until VTAM on the mainframe see's the PU in an
> > active state and the LU is in a SLU ENABLED status.
> >
> > If the PU is active and issuing a second active command allows LU to LU
> > sessions, then I would check the LU and see what its SLU status is. My
> > guess is that it is DISABLED. If so, then either the PU is not telling
> > VTAM when the LU's SLU status become ENABLED, or VTAM is not ENABLING
> > the SLU status when it gets the msg.
> >
> > Rob wrote:
> >
> > > Help
> > >
> > > Pcom v4.2 connects, but no application start for any session until
> > > the PU actived (it is already active), then the apps start.
> > >
> > > Is this a PCOM config or VTAM config?
> > >