I work with Jay and here are the details.
We have mainframe broker and rpc jobs to talk to Natural as a server.
I have a sample trace. Call one is the most recent call from a .NET program to a Natural subprogram through Broker and then a RPC job. This is the call:
W00/ETBXWKR Jan-23-2007 07:40:33 ETBD0282 SPFX Values:
Prefix = 8000051C000001760000001C00000000000001E1000001ED03000000
Unique-ID = 424853462D54544E2D2D30303030303844342D2D3030303030464338
Key string: BID=BHSF-MEDS-ETB210,F=SEND,UID=ERX-USER,CID=NONE,SC=RPC,SN=SRV1,SV=CALLNAT,W
50,SL=346,RL=7900,API=7,CP=0.
Bin string: 04000800F6E890F0A95D1524
The above seems like a normal call to retrieve data, but the next log entry shows a DEREGISTER:
W00/ETBXWKR Jan-23-2007 07:40:33 ETBD0282 SPFX Values:
Prefix = 22010318000000180000000000000000000000000000005A
Unique-ID = 000115C220640000404040404040404000F6DE80C00B86E8D2AA1600
Key string: BID=ETB210,F=DEREGISTER,OP=IMMED,UID=S6,SC=RPC,SN=SRV1,SV=CALLNAT.
And after this, the RPC job goes down and the service is not available. I don’t know if this is because of a Natural error, or something.
The RPC job shows this:
Page 1 01/23/07 07:39:54
#INPUT-ERROR-IND: #INPUT-MESSAGE-TXT:
NAT0082 Invalid command, or Program SCNERP does not exist in library.
FLSH %F
NAT9978 ERROR OCCURRED DURING EXECUTION/COMPILATION
However, program SCNERP is in this library, so it is not missing. And I’m not sure if this error is causing the RPC to go down.
Any ideas?
Dana