The extended status (the D in the tenth position) means that this 
resource was added or moved using Dynamic Reconfiguration.

        If the VTAM resource was built dynamically, it is possible that the 
analogous resource on the as/400 was NOT started.

        One other thought is that I noticed that the new LU does NOT have the 
next consecutive number for the LOCADDR ( 181 vs 214). These number do NOT have 
to be assigned in consecutive order, but they DO HAVE to match. So this LOCADDR 
must match to a corresponding Device address on the AS/400. A mis-match on the 
LOCADDR is enough to prevent the remote device from connecting!!!


  

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Attila Fogarasi
Sent: Wednesday, August 30, 2017 8:16 AM
To: [email protected]
Subject: Re: VTAM SWNET LU status question

The PLU INHIBITED status shows that activation failed with some error sense 
sent by the device, you should be able to find a sense code message earlier at 
time of activation.  To debug you need to trace the x/'0C' control vector on 
NOTIFY or ACTLU RU.  Run VTAM internal trace with OPT=PIU or a BUFFER trace of 
the LU.  Bottom line is that the printer responded that it was not capable with 
some part of the DLOGMODE (which suggests an AS/400 wrong definition for that 
device, different from the working ones unless the printer hardware requires 
some difference).

On Wed, Aug 30, 2017 at 9:21 PM, Tony Thigpen <[email protected]> wrote:

> I have a SWNET PU which attaches to an AS400. The AS400 acts as a 
> print controller with about 200 printer sessions. in this SWNET PU.
>
> We are adding a new LU, but it will not connect. My LU definition is 
> identical to the previously added printer.
>
> Existing, working printer:
> ICU1P634 LU   LOCADDR=181,ISTATUS=ACTIVE,
>                DLOGMOD=RS3262
> New, not-working printer:
> ICU1P635 LU   LOCADDR=214,ISTATUS=ACTIVE,
>                DLOGMOD=RS3262
>
>
> Output of a STATUS command for the non-working printer:
> 06.14.18 HUP1           d net,id=ICU1P635
> 06.14.18 HUP1 STC06991  IST097I DISPLAY ACCEPTED
> 06.14.18 HUP1 STC06991  IST075I NAME = APPN.ICU1P635, TYPE = LOGICAL 
> UNIT IST486I STATUS= ACTIV----D, DESIRED STATE= ACTIV IST1447I 
> REGISTRATION TYPE = NETSRVR IST977I MDLTAB=***NA*** ASLTAB=***NA*** 
> IST861I MODETAB=MODEHUS3 USSTAB=ISTINCNO LOGTAB=***NA*** IST934I 
> DLOGMOD=RS3262 USS LANGTAB=***NA*** IST597I CAPABILITY-PLU 
> INHIBITED,SLU ENABLED  ,SESSION LIMIT 00000001 IST136I SWITCHED SNA 
> MAJOR NODE = SWPUF43 IST081I LINE NAME = LE213000, LINE GROUP = 
> GRPPUF43, MAJNOD = XCAPUF43 IST135I PHYSICAL UNIT = PUF43 IST082I 
> DEVTYPE = LU IST654I I/O TRACE = OFF, BUFFER TRACE = OFF IST1500I 
> STATE TRACE = OFF IST171I ACTIVE SESSIONS = 0000000000, SESSION 
> REQUESTS = 0000000000 IST314I END
>
> There is a new programmer on the AS/400. The person that has done this 
> in the past is gone. I don't know if they have a bad definition or 
> they have not started something right on their end.
>
> When I display the SWNET node, the status shows:
> ICU1P635 ACTIV----D
>
> What does ACTIV----D indicate?
>
> Any thoughts for debugging this?
>
> --
> Tony Thigpen
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send 
> email to [email protected] with the message: INFO IBM-MAIN
>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to