Hi Raymond,

 

Okay, let's get the obvious question out of the way first, you _are_
running this on the z/OS system, and not on VM?

 

Can you test this on another z/OS system to see if it is consistently
wrong? If consistently wrong, then that would suggest a bug.

 

Is z/OS REXX returning something 'extra' at the end of the data that
just looks like it is an extra '1'? (I have no z/OS manuals to check.)

 

Not very helpful, I know, but that's all I can think of.

 

Peter

 

-----Original Message-----
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Raymond Noal
Sent: September 6, 2007 16:46
To: IBMVM@LISTSERV.UARK.EDU
Subject: Me thnks 'Chuckie' is afoot -

 

Ok, you network gurus; I've got one for you - 

The TCP/IP address of my z/OS 1.8 system is 111.222.333.11. (not really,
and yes, I know this is the VM list)

When I run this REXX Exec - 

/*  REXX  */                      

                                  

SAY SOCKET('INITIALIZE','MYID')   

                                  

SAY SOCKET('GETHOSTID');          

                                  

EXIT;                             

The results are:

0 MYID 40 *INET

0 111.222.333.111

Why is the last octet coming back as '111' and not '11'?

TIA

HITACHI
 DATA SYSTEMS 

Raymond E. Noal
Senior Technical Engineer
Office: (408) 970 - 7978 



The information transmitted is intended only for the person or entity to which 
it is addressed and may contain confidential and/or privileged material.  Any 
review retransmission dissemination or other use of or taking of any action in 
reliance upon this information by persons or entities other than the intended 
recipient or delegate is strictly prohibited.  If you received this in error 
please contact the sender and delete the material from any computer.  The 
integrity and security of this message cannot by guaranteed on the Internet.  
The Sender accepts no liability for the content of this e-mail or for the 
consequences of any actions taken on basis of the information provided.  The 
recipient should check this e-mail and any attachments for the presence of 
viruses.  The sender accepts no liability for any damage caused by any virus 
transmitted by this e-mail.  This disclaimer is the property of the TTC and 
must not be altered or circumvented in any manner.

Reply via email to