Reusable Server Kernel

Problem 25 (Minor): RSK and the system node id

=============== 1999-08-12 10:26:49 (-04.00) ===============
 
Name:        ** Suppressed **
Company:     ** Suppressed **
Telephone:   ** Suppressed **
E-mail:      ** Suppressed **
 
Text:
 
The latest bkwlib.vmarc on this web server contains a
fix that will let the RSK tolerate the absence of a
system node name.  The caveat here is that the SPOOL,
MSG/SMSG, and IUCV line drivers might not work correctly,
but RSK facilities that don't care about a node name
(such as the TCP and UDP drivers) should work OK.
Brian
=============== 1999-08-11 19:36:17 (-04.00) ===============
 
Name:        ** Suppressed **
Company:     ** Suppressed **
Telephone:   ** Suppressed **
E-mail:      ** Suppressed **
 
Text:
 
The MSG/SMSG and SPOOL line drivers won't work either.
They use the info returned by QUERY USERID to figure
out what node they're on.
Brian
=============== 1999-08-11 17:31:53 (-04.00) ===============
 
Name:        ** Suppressed **
Company:     ** Suppressed **
Telephone:   ** Suppressed **
E-mail:      ** Suppressed **
 
Text:
 
When using the TCP line driver (and perhaps the UDP line driver as well)
the RSK issues a CP QUERY USERID and parses the response. It
expects the response to be in the standard format of:
   [userid] AT [nodeid]
If the site has a misconfigured System Identifier statement
in the SYSTEM CONFIG file, it is possible that at VM IPL time
the nodeid is set to blanks. This will cause the RSK parser to
fail, and the TCP line driver not to work at all.
The fix is to make sure each site has a valid System Identifier
statement in the SYSTEM CONFIG file.