topic Re: ERROR STATUS = 1432 in ITANIUM Open VMS in Operating System - OpenVMS

ERROR STATUS = 1432 in ITANIUM Open VMS

R SAMANTARAY — Mon, 04 Feb 2008 05:34:43 GMT

Friends,
We are facing a typical problem ,while making UDP communication. This is a FORTAN application. This part of the code shows an IOSB_STATUS error with value 1432.
Can you suggest something ?

Code:

ELSE IF ( MSG_RCV.LINK.IOSB_STATUS .EQ. UDP$_TIMEOUT ) THEN
TYPE *,'MSG_RCV: At ', NOW(),' TIMEOUT'
ELSE
TYPE *,'MSG_RCV: At ', NOW(),' ERROR STATUS=',MSG_RCV.LINK.IOSB_STATUS

ENDIF

*****
INCLUDE FILE

INCLUDE '($SSDEF)/list'

! Added for Open VMS $SSDEF (in Alpha)
! X-K7 MSH1062 MICHAEL S. HARVEY 13-DEC-1990
! ADD SS$_INVARG FOR $CRMPSC AND $MPGBLSC SERVICES
!! PARAMETER SS$_INVARG = '00000FCA'X

PARAMETER UDP$_ABORT = SS$_ABORT ! =0x002c ! Abort */
PARAMETER UDP$_BADDATA = SS$_BADCHKSUM ! =0X0808 ! Bad/invalid data re
ad */
PARAMETER UDP$_BADPARAM = SS$_BADPARAM ! =0x0014 ! Bad parameter value
*/
PARAMETER UDP$_BUFFEROVF = SS$_BUFFEROVF ! =0x0601 ! Buffer overflow
*/
PARAMETER UDP$_CANCEL = SS$_CANCEL ! =0x830 ! Operation Canceled
*/
PARAMETER UDP$_CONNECFAIL = SS$_CONNECFAIL ! =0x20dc ! Connection Timed-Ou
t or failed */
PARAMETER UDP$_DATAOVERUN = SS$_DATAOVERUN ! =0x0838 ! Data Overrun */
PARAMETER UDP$_INSFMEM = SS$_INSFMEM ! =0x0124 ! Insufficent memory
!! PARAMETER UDP$_INVARG = SS$_INVARG ! =0x0fca ! Invalid Argument(s)
*/
PARAMETER UDP$_LINKABORT = SS$_LINKABORT ! =0x20e4 ! Link Abort */
PARAMETER UDP$_LINKDISCON = SS$_LINKDISCON ! =0x20ec ! Link Disconnected *
/
PARAMETER UDP$_LINKEXIT = SS$_LINKEXIT ! =0x20f4 ! Link Exit */
PARAMETER UDP$_NODATA = SS$_NODATA ! =0x01ac ! No data */
PARAMETER UDP$_NORMAL = SS$_NORMAL ! =0x0001 ! Service Completed s
uccessfully */
PARAMETER UDP$_REJECT = SS$_REJECT ! =0x0294 ! Connection Request
Rejected */
PARAMETER UDP$_TIMEOUT = SS$_TIMEOUT ! =0x022c ! Operation timed out
*/
PARAMETER UDP$_TOOMUCHDATA= SS$_TOOMUCHDATA! =0x029c ! Too much data */

STRUCTURE /UDP_LINK_STC/
INTEGER*4 CHANNEL
INTEGER*4 SOCK_ADDR1(4)
INTEGER*4 A_DATA
INTEGER*4 DATA_SIZE
INTEGER*2 IOSB_STATUS
INTEGER*2 IOSB_BYTES
INTEGER*4 IOSB_RESERVED
INTEGER*4 TIMEOUT_DT(2)
INTEGER*4 TIMER_ID
INTEGER*4 EFN
INTEGER*4 A_AST(2)
END STRUCTURE

Re: ERROR STATUS = 1432 in ITANIUM Open VMS

Hein van den Heuvel — Mon, 04 Feb 2008 06:19:06 GMT

What is the primary error status?
That is... the status of the call itself. (r0 in debugger)

Is the field initialized?
If the call completely fails, then the IOSB_STATUS will not be filled in.
What is the value before the IO call?

Did the code ever work? On Alpha? On itanium?
What does the actual IO call look like?
Is the return variable properly declared as int?

1432 in decimal would be SUBRNG6
I've never seen that in decades of OpenVMS usage.
1432 in hex does not appear to be valid.

Hth,
Hein.

Re: ERROR STATUS = 1432 in ITANIUM Open VMS

R SAMANTARAY — Mon, 04 Feb 2008 09:51:10 GMT

Yes,

This is working in another ITANIUM server with VMS8.2. The current server is with VMS8.3.

Re: ERROR STATUS = 1432 in ITANIUM Open VMS

Hein van den Heuvel — Mon, 04 Feb 2008 12:16:23 GMT

So maybe this is a new server where the network is not setup as the old one?
I assume that basic stuff works... telnet, ssh, ftp.

Is the 8.2 system still available and was the 8.3 fresh created or was it upgraded?
For a fresh create, maybe the usernames are set up differently? Do a $show proc/all or a piecemeal $show proc/quota, $show quota /priv and compare?

Where is the program connecting?
Can you use the same username, but an other tool to try that connection? Just use ping first, then telnet to the target node/port.

Anything in any system logs?
Error count on the ethernet/internet interface?
(Security) auditing entries?

And I'm still interested in the IO call return status and the immediate code adn declarations used in that area of the code.

Hth,
Hein.