IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.


#TechXchangePresenter
 View Only
Expand all | Collapse all

NATSRVD 7610 NAT0954 Abnormal termination S0C1 .....

  • 1.  NATSRVD 7610 NAT0954 Abnormal termination S0C1 .....

    Posted Wed November 26, 2008 01:22 AM

    One subtask of our production RPC server terminated with S0C1 and another subtask received the access-denied-message. The RPC server was cancelled and restarted (see the parameters).

    SL24 had for a similar problem and for Natural version 3 the following solution - but we are running NAT423.
    NSC - NAT1696 logon to library failed because logoff failed RC=12 NATSRVD line 7610

    ETID=FRCEBLNK,
    BPI=(TYPE=NAT NAME=N423P56),
    DSIZE=0,
    WSIZE=1,
    ESIZE=64,
    SSIZE=0,
    STACK=(LOGON PDSTMAIN,STRPCP,PRODxx),
    RCA=(BROKER),
    RCALIAS=(BROKER,BKIMBTSO),
    RPC=(SERVER=ON,ACIVERS=4,LOGONRQ=ON,SRVUSER=‘*NSC’),
    RPC=(SRVNAME=STRPCR01,SRVNODE=‘xxx.yyy.32.5:18214:TCP’),
    RPC=(RPCSIZE=5040,MAXBUFF=5000),
    RPC=(NTASKS=6,TRACE=(1,E)),

    *** Initialize a Natural RPC server at 2008-11-24 11:13:56
    *** with name STRPCR01
    *** on host SY5
    *** under z/OS 01.09.00
    *** Natural nucleus version : 4.2.3
    *** Natural system file version : 4.2.4 service pack 3
    *** Natural RPC version : 6.2.3 update level 1
    *** Highest supported RPC protocol: 2020
    *** SYSIDL version : 6.1.1.8
    *** Natural server library : PDSTMAIN
    *** Natural server user ID : STRPCP
    *** Natural security activated : Yes
    *** Logon data required (LOGONRQ) : Yes
    *** System file settings
    *** FUSER = ( 134 , 205 )
    *** FNAT = ( 240 , 54 )
    *** FSEC = ( 134 , 204 )

    *** Steplib settings
    *** PDSTMAIN ( 134 , 205 )
    *** PDSTSYS ( 134 , 205 )
    *** PDSTETRX ( 134 , 205 )
    *** SYSTEM ( 134 , 205 )
    *** SYSTEM ( 240 , 54 )
    *** Natural security settings according to RPC server profile
    *** Timestamp related ETID : N
    *** Parameters for transport
    *** Server (SRVNAME) : STRPCR01
    *** Node (SRVNODE) : xxx.yyy.32.5:18214:TCP
    *** User ID (SRVUSER) : *NSC
    *** Buffer (MAXBUFF) : 5120000 bytes
    *** Version (ACIVERS) : 4
    *** Code page (CPRPC) : N/A
    EntireX Broker Stub Version=7.2.1, Patch Level=92, Highest API Supported=8
    *** Natural server environment successfully initialized at 11:13:57
    *** LOGON to Broker xxx.yyy.32.5:18214:TCP at 11:13:57
    *** Initialization of transport successful at 11:13:57
    *** Subtask 1 successfully attached
    *** Subtask 2 successfully attached
    *** Subtask 3 successfully attached
    *** Subtask 4 successfully attached
    *** Subtask 5 successfully attached

    NAT9974 Natural termination forced by abend S222.

    Subtask

    NATSRVD 7610 NAT0954 Abnormal termination S0C1 during program execution.
    SARPAGE 11
    NAT9978 Error occurred during execution/compilation.

    Subtask

    ********** USER-ID: STRPCP LIB : PDSTMAIN
    B *** Last request received at 2008-11-24 11:40:05
    FUNCTION: L RC: 7 SERVER: STRPCR01
    00080353 Access Denied Bad STOKEN: UID/PWD needed…*…
    SEND-LEN: 5120000 REC-LEN: 0
    M *** RC 7 from listen request. Server terminates
    MC *** Server is terminated at 2008-11-24 11:40:05

    Other Subtasks:
    NAT9974 Natural termination forced by abend S222.

    We don’t use the EntireX Broker version 8.

    Any suggestions?

    Thanks,
    Dieter Storr


    #Mainframe-Integration
    #EntireX
    #webMethods


  • 2.  RE: NATSRVD 7610 NAT0954 Abnormal termination S0C1 .....

    Posted Tue December 02, 2008 10:58 AM

    Hi Dieter,

    I sugest that you contact support regarding this issue.


    #Mainframe-Integration
    #EntireX
    #webMethods