SYMUPDTE has not existed for many years. There is IEASYMUP. If you are 
using SYMUPDTE, I suggest that you change.

"Supported" is an interesting term. I might say that "supported" means 
documented and that we will take an APAR if there is an error. I might say 
that IEASYMUP meets both of those qualifications. The documentation is in 
the Redbook and, as with any sample, we will take APARs if there is an 
error. But I know that's not what you had in mind, and having to linkedit 
IEASYMUP yourself is far from ideal.

As to "why not yet", it is in part because we had asked for, but until the 
Share requirement mentioned had not received, a requirement that said that 
it was OK not to have remote systems update their copies of the symbols 
from "this system" when "this system" changed symbols (whether added or 
deleted).  That is the expensive thing, and is a logical step, but is not 
clear when we would choose to spend the resources to implement it. This is 
the thing that IEASYMUP does not do.

Are the return codes really not documented in the Redbook? Sorry about 
that. 

(hex)
00000000 - Success
00000008 - No parameter provided 
nnnnnn0C - Symbol name contains ampersand 
nnnnnn10 - Symbol name length, without ampersand, 
           is not 1-8 
nnnnnn14 - Symbol value length > symbol name length 
           minus 1 
00000018 - Too many symbols (maximum number of 
           symbols is exceeded) 
nnnnnn1C - Reserved symbol 
nnnnnn20 - Security product denied access 
nnnnnn24 - Symbol value contains ampersand 

In the info above, "nnnnnn" is a 1-origin number identifying which symbol 
the processing did not like.

By the way: If / When updating of symbols is "fully supported", it might 
not be via an EXEC PGM= program such as IEASYMUP. If IEASYMUP is 
supplanted by another mechanism, a new IEASYMUP might be provided which 
does nothing more than return a new return code indicating "do not use 
me".  We would not be able reasonably to do much more than warn / alert 
you not to use an "old" IEASYMUP as an old IEASYMUP might not build the 
control structures expected. 

Peter Relson
z/OS Core Technology Design

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to