AS/400, Having problems with IP over SNA

comp.sys.ibm.as400.misc - IBM AS/400 miscellaneous topics.


AS/400 >> Having problems with IP over SNA

by calronphx » Fri, 19 Sep 2003 07:25:03 GMT

We are trying to setup a controller on a AS/400 OS/400 V5R2M0 to do
3270 access to our VM/VSE mainframe. We are running IP over SNA.
Have changed network attribute Allow AnyNet support to *yes. Below is
the message received when varying on the controller. Also noticed a
few messages WRKJOB QLUS.

No interfaces defined for IPS or IPI support. F1 says:

Message ID . . . . . . : CPDA12C Severity . . . . . . . : 30
Message type . . . . . : Diagnostic
Date sent . . . . . . : 09/15/03 Time sent . . . . . . :
00:38:09

Message . . . . : No interfaces defined for IPS or IPI support.
Cause . . . . . : AnyNet/400 IP over SNA (IPS) and AnyNet/400 IP
over IPX
(IPI) support are not activated because there are no interfaces
defined for
either function. The Allow ANYNET support (ALWANYNET) network
attribute
parameter remains set to *YES. The AnyNet/400 APPC over TCP and
AnyNet/400
APPC over IPX functions are activated.
Recovery . . . : To activate AnyNet/400 IP over SNA or IP over IPX
support
do the following:
-- Add an IP over SNA interface using the Add IP over SNA
Interface
(ADDIPSIFC) CL command, or add an IP over IPX interface using the
Add IP
over IPX Interface (ADDIPIIFC) CL command.
-- Issue the Change Network Attributes (CHGNETA) CL command with
the Allow
ANYNET support (ALWANYNET) parameter set to *NO. Then issue the
CHGNETA CL
command again with the ALWANYNET parameter set to *YES.
Interfaces are activated by default when AnyNet/400 support is
activated.
If you do not want an interface to be active, issue the End IP over
SNA
Interface (ENDIPSIFC) CL command or the End IP over IPX Interface
(ENDIPIIFC) CL command to deactivate the interface.

Also noticed:IP over SNA not activated F1 says:

Message ID . . . . . . : CPFA11A Severity . . . . . . . :
40
Message type . . . . . : Diagnostic
Date sent . . . . . . : 09/15/03 Time sent . . . . . . :
00:38:09

Message . . . . : IP over SNA not activated.
Cause . . . . . : IP over SNA activation was attempted as a result
of the
Change Network Attributes (CHGNETA) CL command being issued with
the allow
AnyNet support (ALWANYNET) parameter set to *YES. However, errors
occurred
during IP over SNA protocol stack activation that prevented it from
being
activated.
Recovery . . . : See the messages listed previous to this message
in the
QLUS job log. To view the QLUS job log, issue the Work with Job
(WRKJOB) CL
command with the job name (JOB) parameter set to QLUS, locate the
QLUS job
entry with a status of active in the list, and then select option
1, Select.
Correct the errors and then try activating the IP over SNA protocol
stack
again. To retry IP over SNA activation, issue the CHGNETA CL
command with
ALWANYNET set to *NO and then issue the command again with ALWANYNET
set to
*YES.







Message ID . . . . . . : CPA5714 Severity . . . . . . . : 60
Message type . . . . . : Inquiry
Date sent . . . . . . : 09/18/03 Time sent . . . . . . :
15:19:01

Message . . . . : System cannot call controller HOST. No lines
available. (C
R)
Cause . . . . . : When attempting to call out using controller HOST,
the
system was unable to connect controller HOST to a line description
found in
the switched line list (SWTLINLST). The most common reason for this
failure
is that none of the line descriptions in the switched line list is
in the
proper state to call out.
Other possible reasons a line is not selected are:
-- The maximum number of active controllers (MAXCTL parameter) for a
line
description has been exceeded.
-- There are no lines in the switched line list (SWTLINLST
parameter) of the
controller description.
-- A line description may be attached to the *INTERNAL port of a
*BASE NWSD.
-- Controller HOST runs over a protocol other than TCP/IP, and each
of the
line descriptions found in the switched line list (SWTLINLST)
specifies a
hardware resource (RSRCNAME parmeter) that only supports TCP/IP.
Recovery . . . :
Use the Work with Controller Description (WRKCTLD) command to
display the
switched line list (SWTLINLST parameter) for controller HOST. If
there are
no lines configured in the switched line list, add the name of the
line
description to be used for the call.
If there are line descriptions configured in the switched line
list, press
F14 to run problem analysis. This will display a list of line
descriptions
that were unable to be selected for the call. Each line description
will
have a corresponding failure cause indicating why it was not selected
at
time the call was attempted. Follow the recovery actions specified
for t
line description intended to be used. Then type R to retry the call.
ossible choices for replying to message . . . . . . . . . . . . . . .
:
C -- The system will inform any applications or subsystems that are
waiti
for the connection that the connection cannot be made.
R -- The system will try to call the controller again.
echnical description . . . . . . . . : The error log identifier is

Line description . . . . . . . . . : ETHL2
Option . . . . . . . . . . . . . . : *BASIC
Category of line . . . . . . . . . : *ELAN

Resource name . . . . . . . . . . : CMN12
Online at IPL . . . . . . . . . . : *NO
Vary on wait . . . . . . . . . . . : *NOWAIT
Network controller . . . . . . . . : ETHL2NET
Local adapter address . . . . . . : 0006296B7928
Exchange identifier . . . . . . . : 05620302
Ethernet standard . . . . . . . . : *ALL
Line speed . . . . . . . . . . . . : *AUTO
Current line speed . . . . . . . . : 100M
Duplex . . . . . . . . . . . . . . : *FULL
Current duplex . . . . . . . . . . : *FULL
Maximum frame size . . . . . . . . : 1496
Maximum controllers . . . . . . . : 40
Line description . . . . . . . . . : ETHL2
Option . . . . . . . . . . . . . . : *BASIC
Category of line . . . . . . . . . : *ELAN

Error threshold level . . . . . . : *OFF
Generate test frame . . . . . . . : *YES
Message queue . . . . . . . . . . : *SYSVAL
Current message queue . . . . . . : QSYSOPR
Library . . . . . . . . . . . . : QSYS
Text . . . . . . . . . . . . . . . : 1Gbps Ethernet

Controller description . . . . . . : HOST
Option . . . . . . . . . . . . . . : *BASIC
Category of controller . . . . . . : *HOST

Link type . . . . . . . . . . . . : *LAN
Online at IPL . . . . . . . . . . : *YES
Switched connection . . . . . . . : *YES
Character code . . . . . . . . . . : *EBCDIC
Maximum frame size . . . . . . . . : 16393
Current maximum frame size . . . . : 0
Remote network identifier . . . . : USACBC01
Remote control point . . . . . . . : ACBCDRM1
SSCP identifier . . . . . . . . . : 051000000001
Local exchange identifier . . . . : 05612122
Initial connection . . . . . . . . : *DIAL
Dial initiation . . . . . . . . . : *LINKTYPE
Controller description . . . . . . : HOST
Option . . . . . . . . . . . . . . : *BASIC
Category of controller . . . . . . : *HOST

Switched disconnect . . . . . . . : *NO
LAN remote adapter address . . . . : 0200ECA44080
LAN DSAP . . . . . . . . . . . . . : 04
LAN SSAP . . . . . . . . . . . . . : 04
System job . . . . . . . . . . . . : QCMNARB03
Message queue . . . . . . . . . . : *SYSVAL
Current message queue . . . . . . : QSYSOPR
Library . . . . . . . . . . . . : QSYS
Text . . . . . . . . . . . . . . . : 3270 Emulation to HOST
Mainframe



X'80000205'.

Any help with direction where to go from here would be wonderful.
Top

AS/400 >> Having problems with IP over SNA

by Bengt Persson » Fri, 19 Sep 2003 14:57:46 GMT


NA over IP is on every mans AS/400 since ages, but what in the world
is "IP over SNA" and who would ever want it and for what?
Please educate me anyone?

You have a typical SNA Host controller there. Is it connected to the Line?
CHGCTLHOST HOST SWTLINLST(ETHL2)
Then it should go active if You have SNA running in Your net all the way to
the
Mainframe. Of course there has to be matching definitions in VTAM in status
"connectable".

If it's just for 3270 access you can just do Telnet MainframeIPAddress from
the AS/400. Then you don't need any HOST-controller at all.

"Ron Maddox" < XXXX@XXXXX.COM > skrev i meddelandet
news: XXXX@XXXXX.COM ...


Top
Similar Threads

1. bsc/sdlc/sna over ip??? 

I have a client that have 2 as/400's, one is adv/36 without os/400 and the
other has adv/36 running as a guest.

They have the two interconnect via a dial up connection. The quality of the
phone lines are poor so best they can connect is 19.2. They also have a remote
"5394" at another location same problem. 

The ideal solution would be to get some box that would take the bsc/rs232
connection, convert it to something that was routable over the internet in some
encrypted format (info being transferred is not "sensitive"), and on the other
end convert it back. Of course, each would have a broadband internet connection
with a static ip address...

anybody doing this and how has it worked...

I realize that if they were on the os/400 level, there are things they could do
via ethernet, but this is not what they have or want to do...

chris

2. Having problems with DestroyJavaVM in V5R3 - AS/400

3. I'm having problems with Far Cry in my new PC 


I used to play Far Cry in a PC I bought in early 2002 and it's great
fun although I could not put all the settings on maximum otherwise it
slowed doew a bit but it was still visually stunning even at 1600 X
1200 and setting on medium low.

Now I bought a new PC and of course I put all settings on maximum and
it's even better graphically but there's something wrong with the
colours, some of them are too bright, too intense almost like a bright
blur at some points. I am not experiencing this with other games so I
assume there's something imcompatible between Far Cry and my new PC.
The guy who sold me the PC tells me that the Graphics Card is too
recent for Far Cry, I'm not sure if that's the problem.

Specifically it seems everything is a bit too yellow, very bright
yellow. For example the floors of the cabanas aren't yellow, they are
bright white and some of the walls are a bright yellowish and as I move
into the game some of the blues are also too bright.
In my other PC the cement was grey, here it seems yellow with as touch
of green, more in some portions of the game.

The tide's water also seems a darker blue rather than the clearer blue
in my other PC which was more beautiful IMHO. BTW, the game now has
fireflies, LOL. These didn't appear in the game in my other PC, pretty
cool.

Another small problem I experience is that if I have everything on
maximum but shadows on medium it's cool but if I move shadows to high
of very high I start seeing black spots in the floor of the game, these
very black square shaped shadow spots are about the size of a cabana
and are visible very early in the game after you get the transmiter and
the desert eagle and walk out of the tunnel and below are the cabanas
and small pier and with shadows on max I see black spots on the floor
of the hill, beach, pier, etc
I can live with the shadow spots but if i could fix the bright colours
that would be nice.

Anyway, hope there's a patch or driver or whatever that can fix these
bright colours because it's really a shame. Many thanks.



Andr

4. Having problems installing KOTOR.

5. Nvidia having problems with its upcoming flagship NV55 / G92 / GeForce 9800 GPU

6. In Memorium - having problems with videos not displaying (help required)

7. Counterstrike having problems on Dell laptop 

A friend's kid is having problems playing Counterstrike 3D v 1.6 on a
Dell laptop.

Dell is an Inspiron 5150. I do not recognize the video card right away
but here are the specs and the operating system:

SXGA+,P4 3.06gHZ
384 MB
64MB ATi MOBILITY RADEON 9000
WINDOWS XP HOME

I have a suspicion that this configuration does not have the
appropriate video card for this game.

Any comments?

Thanks!

Sam
[PLEASE do not e-mail me, my address is spam-proofed.]

8. Anyone having problem with Oblivion DVD ?