SNA: RS/6000 <-> IBM mainframe

SNA: RS/6000 <-> IBM mainframe

Post by Johnny Ch » Fri, 07 Dec 1990 10:10:38



        Here is my second question about SNA connection:

        We cannot set up a connection between an RS/6000 workstation and
an IBM 3090 mainframe through a leased telephone line using SDLC and let
the workstation talk to the mainframe using LU6.2 protocol.

        The IBM 3090 runs MVS and VTAM. The RS/6000 workstation contains
a 4-port Multiprotocol adapter and connects to an IBM 7861-047 modem.

        These are the errors we get after running "smit problem":

---------------------------------------------------------------------------
ERROR LABEL:    SNA_OMDDF
ERROR ID:       F0571D9F

Date/Time:       Dec 05 14:24:06
Sequence Number: 6683
Machine Id:      000006103000
Node Id:         lakers
Error Class:     S
Error Type:      Perm
Resource Name:   SNA    

Error Description
SOFTWARE PROGRAM ERROR

Probable Causes
SNA COMMUNICATIONS

Failure Causes
Open to SNA MDD failed

        Recommended Actions
        IF PROBLEM PERSISTS THEN DO THE FOLLOWING
        REPORT THE FOLLOWING

Detail Data
COMPONENT ID
LUXCR              
DETECTING MODULE
srmbacb.c          
Module Line Number:
         119
ERROR CODE
         255
---------------------------------------------------------------------------
ERROR LABEL:    SNA_SRF
ERROR ID:       265D71E6

Date/Time:       Dec 05 14:24:06
Sequence Number: 6682
Machine Id:      000006103000
Node Id:         lakers
Error Class:     S
Error Type:      Perm
Resource Name:   SNA    

Error Description
SOFTWARE PROGRAM ERROR

Probable Causes
SNA COMMUNICATIONS

Failure Causes
SNA system resource failure

        Recommended Actions
        IF PROBLEM PERSISTS THEN DO THE FOLLOWING
        REPORT THE FOLLOWING

Detail Data
COMPONENT ID
SNA_MDD            
DETECTING MODULE
luxioctl.c          
Module Line Number:
         362
ERROR CODE
          -1
---------------------------------------------------------------------------
ERROR LABEL:    SNA_IPCF
ERROR ID:       AD6D66AF

Date/Time:       Dec 05 14:24:06
Sequence Number: 6681
Machine Id:      000006103000
Node Id:         lakers
Error Class:     S
Error Type:      Perm
Resource Name:   SNA    

Error Description
SOFTWARE PROGRAM ERROR

Probable Causes
SNA COMMUNICATIONS

Failure Causes
SNA IPC failure

        Recommended Actions
        Increase IPC System Resources
        IF PROBLEM PERSISTS THEN DO THE FOLLOWING
        REPORT THE FOLLOWING

Detail Data
COMPONENT ID
LUXLNS              
DETECTING MODULE
luxlnsm.c          
Module Line Number:
         472
ERROR CODE
          36
---------------------------------------------------------------------------
ERROR LABEL:    SNA_IPCF
ERROR ID:       AD6D66AF

Date/Time:       Dec 05 14:24:06
Sequence Number: 6680
Machine Id:      000006103000
Node Id:         lakers
Error Class:     S
Error Type:      Perm
Resource Name:   SNA    

Error Description
SOFTWARE PROGRAM ERROR

Probable Causes
SNA COMMUNICATIONS

Failure Causes
SNA IPC failure

        Recommended Actions
        Increase IPC System Resources
        IF PROBLEM PERSISTS THEN DO THE FOLLOWING
        REPORT THE FOLLOWING

Detail Data
COMPONENT ID
LUXLRM              
DETECTING MODULE
luxlrm.c            
Module Line Number:
         338
ERROR CODE
          36
---------------------------------------------------------------------------
ERROR LABEL:    SNA_IPCF
ERROR ID:       AD6D66AF

Date/Time:       Dec 05 14:24:06
Sequence Number: 6679
Machine Id:      000006103000
Node Id:         lakers
Error Class:     S
Error Type:      Perm
Resource Name:   SNA    

Error Description
SOFTWARE PROGRAM ERROR

Probable Causes
SNA COMMUNICATIONS

Failure Causes
SNA IPC failure

        Recommended Actions
        Increase IPC System Resources
        IF PROBLEM PERSISTS THEN DO THE FOLLOWING
        REPORT THE FOLLOWING

Detail Data
COMPONENT ID
LUXCPS              
DETECTING MODULE
luxrout.c          
Module Line Number:
         160
ERROR CODE
          36
---------------------------------------------------------------------------
ERROR LABEL:    SRC
ERROR ID:       E18E984F

Date/Time:       Dec 05 14:23:47
Sequence Number: 6678
Machine Id:      000006103000
Node Id:         lakers
Error Class:     S
Error Type:      PERM
Resource Name:   SRC

Error Description
SOFTWARE PROGRAM ERROR

Probable Causes
APPLICATION PROGRAM

Failure Causes
SOFTWARE PROGRAM

        Recommended Actions
        PERFORM PROBLEM RECOVERY PROCEDURES

Detail Data
SYMPTOM CODE
           0
SOFTWARE ERROR CODE
       -9017
ERROR CODE
           9
DETECTING MODULE
'srchevn.c'@line:'268'
FAILING MODULE
sna

        And the following are our profiles :

CDEFAULT_CONNECTION:
        type = CONNECTION
        profile_name = CDEFAULT
        attachment_name = RDEFAULT
        local_lu_name = LDEFAULT
        network_name =
        remote_lu_name =
        stop_connection_on_inactivity = no
        lu_type = lu6.2
        interface_type = extended
        remote_tpn_list_name = RDEFAULT
        mode_list_name = MDEFAULT
        node_verification = no
        inactivity_timeout_value = 0
        notify = no
        cp_sessions = no
        parallel_sessions = single
        negotiate_session_limits = no

AXLCP_CONNECTION:
        type = CONNECTION
        profile_name = AXLCP
        attachment_name = AXAP
        local_lu_name = AXLLUP
        network_name = LAXWCO00
        remote_lu_name = XCOMAPPL
        stop_connection_on_inactivity = no
        lu_type = lu6.2
        interface_type = extended
        remote_tpn_list_name = AXRTPNLP
        mode_list_name = MDEFAULT
        node_verification = no
        inactivity_timeout_value = 0
        notify = no
        cp_sessions = no
        parallel_sessions = single
        negotiate_session_limits = no

LDEFAULT_LOCALLU:
        type = LOCALLU
        profile_name = LDEFAULT
        local_lu_name =
        network_name =
        lu_type = lu6.2
        independent_lu = yes
        cp_sessions = no
        tpn_list_name = TDEFAULT
        local_lu_address = 1
        sscp_id =
        number_of_rows = 24
        number_of_columns = 80

AXLLUP_LOCALLU:
        type = LOCALLU
        profile_name = AXLLUP
        local_lu_name = N15023L0
        network_name = LAXWCO00
        lu_type = lu6.2
        independent_lu = yes
        cp_sessions = no
        tpn_list_name = AXTPNLP
        local_lu_address = 2
        sscp_id = 000000000007
        number_of_rows = 24
        number_of_columns = 80

EDEFAULT_ATTACHMENT:
        type = ATTACHMENT
        profile_name = EDEFAULT
        control_point_profile_name = CDEFAULT
        logical_link_profile_name = EDEFAULT
        physical_link_profile_name = EDEFAULT
        logical_link_type = ethernet
        stop_attachment_on_inactivity = no
        station_type = secondary
        physical_link_type = ethernet
        remote_secondary_station_address = 1
        smart_modem_command_sequence =
        length_of_command_sequence = 0
        call_type = listen
        x25_level = 1984
        listen_name = IBMQLLC
        autolisten = no
        timeout_value = 0
        remote_link_name_ethernet =
        remote_link_name_token_ring =
        remote_link_address_token_ring = 000000000000
        selection_sequence =
        length_of_selection_sequence = 0
        network_type = switched
        access_routing = link_name
        remote_sap_address = 04
        remote_sap_address_range_lower = 04
        remote_sap_address_range_upper = EC
        virtual_circuit_type = permanent
        remote_station_X.25_address =
        optional_X.25_facilities = no
        logical_channel_number_of_PVC = 1
        reverse_charging = no
        rpoa = no
        default_packet_size = yes
        default_window_size = yes
        default_throughput_class = yes
        closed_user_group = no
        closed_user_group_outgoing = no
        network_user_id = no
        network_user_id_name =
        data_network_identification_code =
        packet_size_for_received_data = 128
        packet_size_for_transmit_data = 128
        window_size_for_received_data = 2
        window_size_for_transmit_data = 2
        throughput_class_for_received_data = 1200
        throughput_class_for_transmit_data = 1200
        index_to_selected_closed_user_group = 0
        lu_address_registration = no
        lu_address_registration_name = LDEFAULT

RDEFAULT_ATTACHMENT:
        type = ATTACHMENT
        profile_name = RDEFAULT
        control_point_profile_name = CDEFAULT
        logical_link_profile_name = SDEFAULT
        physical_link_profile_name = RDEFAULT
        logical_link_type = sdlc
        stop_attachment_on_inactivity = no
        station_type = secondary
        physical_link_type = eia232d
        remote_secondary_station_address = 1
        smart_modem_command_sequence =
        length_of_command_sequence = 0
        call_type = listen
        x25_level = 1984
        listen_name = IBMQLLC
        autolisten = no
        timeout_value = 0
        remote_link_name_ethernet =
        remote_link_name_token_ring =
        remote_link_address_token_ring = 000000000000
        selection_sequence =
        length_of_selection_sequence = 0
        network_type = switched
        access_routing = link_name
        remote_sap_address = 04
        remote_sap_address_range_lower = 04
        remote_sap_address_range_upper = EC
        virtual_circuit_type = switched
        remote_station_X.25_address =
        optional_X.25_facilities = no
        logical_channel_number_of_PVC = 1
        reverse_charging = no
        rpoa = no
        default_packet_size = yes
        default_window_size = yes
        default_throughput_class = yes
        closed_user_group = no
        closed_user_group_outgoing = no
        network_user_id = no
        network_user_id_name =
        data_network_identification_code =
        packet_size_for_received_data = 128
        packet_size_for_transmit_data = 128
        window_size_for_received_data = 2
        window_size_for_transmit_data = 2
        throughput_class_for_received_data = 9600
        throughput_class_for_transmit_data = 9600
        index_to_selected_closed_user_group = 0
        lu_address_registration = no
        lu_address_registration_name = LDEFAULT

TDEFAULT_ATTACHMENT:
        type = ATTACHMENT
        profile_name = TDEFAULT
        control_point_profile_name = CDEFAULT
        logical_link_profile_name = TDEFAULT
        physical_link_profile_name = TDEFAULT
        logical_link_type = token_ring
        stop_attachment_on_inactivity = no
        station_type = secondary
        physical_link_type = token_ring
        remote_secondary_station_address = 1
        smart_modem_command_sequence =
        length_of_command_sequence = 0
        call_type = listen
        x25_level = 1984
        listen_name = IBMQLLC
        autolisten = no
        timeout_value = 0
        remote_link_name_ethernet =
        remote_link_name_token_ring =
        remote_link_address_token_ring = 000000000000
        selection_sequence =
        length_of_selection_sequence = 0
        network_type = switched
        access_routing = link_name
        remote_sap_address = 04
        remote_sap_address_range_lower = 04
        remote_sap_address_range_upper = EC
        virtual_circuit_type = switched
        remote_station_X.25_address =
        optional_X.25_facilities = no
        logical_channel_number_of_PVC = 1
        reverse_charging = no
        rpoa = no
        default_packet_size = yes
        default_window_size = yes
        default_throughput_class = yes
...

read more »

 
 
 

SNA: RS/6000 <-> IBM mainframe

Post by Johnny Ch » Fri, 07 Dec 1990 09:21:52


        How can we set up a connection between an RS/6000 workstation and
an IBM 3090 mainframe through a leased telephone line using SDLC and let
the workstation emulate an IBM 3270 data terminal?

        The IBM 3090 runs MVS and TSO/VTAM. The RS/6000 workstation contains
a 4-port Multiprotocol adapter and connects to an IBM 5822-10 modem.

        Are we using the right hardware configuration ? What is the procedure
to set up the connection in terms of mainframe side and workstation side ?
Finally, where can we find related documentation ?

        Thank You !

        Johnny Chao


 
 
 

1. SNA file transfer between RS/6000 and mainframe

This may be a repost (we had some problems with our
news feed).  If so, please ignore...

I think this is a very simple question, but I don't know
the answer:

We have a mainframe (IBM 4381 running MVS/TSO) connected to
a token ring via a 3745.  We also have an RS/6000 that we
can put on that token ring.  For various reasons (including cost),
it is not possible to get TCP/IP software on the mainframe (we're
also not sure whether we can run TCP/IP on the host with this hardware
configuration).

Given these circumstances, it seems natural to communicate with
the host via SNA.  Our needs are fairly limited: currently,
we just need to do unattended file transfers.  A program analagous
to the TCP/IP ftp program would be perfect.  Unfortunately, I
know nothing about SNA.  As I understand it, AIX 3.1 comes with
support for SNA services.  Does anyone know what we need to do
to support this type of communication?  Is there a standard
SNAftp program?

An additional question: currently, the RS/6000 is connected to
an ethernet that is gated onto the token ring by a Cisco.
Would it be possible to conduct the SNA communications through the
Cisco gateway?  If not, we would just put the RS/6000 on the
token ring.

Thanks in advance,
Andy

2. OOPS: Multipath routing 2.4.17

3. AIX System Admin/ RS-6000 <<>> Nationwide Opportunities

4. Java makefile on Solaris

5. IBM RS/6000 <==> Novell

6. How does the client know when to stop reading from a socket

7. <><><> MOUNTING EXTENDED PARTITION <><><>

8. Using mouse on COM2: ?

9. RS/6000 to IBM MainFrame

10. Wanted: <><><> Unix Specialist <><><>

11. LILO help <><><><><><>

12. RS/6000->AS/400, via SNA

13. RS/6000 <=> AS/400