One point to remember, the length of the value of a symbol definition may not be longer that the length of the symbol including the '&'. In your example, you probably meant to say SYMDEF(&REL='V3R4') which would work fine since both lengths are 4.
Also remember that for LPA/LINK lists, if applicable , the 'real' name must be used, not the alias name. IMO bad thing about SYMBOLICRELATE is that the value of the symbol cannot be changed without IPLing the system - AFAIK nothing has been provided as of yet to dynamically change a symbols value. Don't mean to nit-pick but having gotten bitten by that before, I never forget it. Guy Gardoit z/OS Systems Programming On Fri, Jan 23, 2009 at 5:27 AM, Blair Svihra < [email protected]> wrote: > Review figure 38 on page 44 in the manual Bruno Sugliani referenced - > http://www.redbooks.ibm.com/redbooks/pdfs/sg245336.pdf > > What is not clear from the example is your user will use SYS5.MQ.whatever > in their JCL (JCL never has to change) but will reference > SYS5.MQ.XXXX.whatever where XXXX is a symbol for the current version. You > can update the symbolic when you change releases without requiring the user > to update JCL. > > IEASYMxx > . > . > SYMDEF(&rel='&v3R4') > > DEFINE ALIAS(NAME('SYS5.MQ.WHATEVER') SYMRELATE('SYS5.MQ.&REL.WHATEVER')) > > > In th JCL > //DD1 DD DSN=SYS5.MQ.whatever,DISP=SHR > > > -- > Blair Svihra > Dino-Software Corporation > 800-480-DINO > www.dino-software.com > > Dino-Software Utilities > T-REX – Superior catalog management tool inclusive of HSM & Tape audits > REORGadon – First REORG While-OPEN tool for HSM > Teradon – First ever OnLine REPRO MERGECAT utility > Xtinct - DASD Data purge > RTD - DASD Real Time Defrag > DAL – Analysis for Legato in an easy to view format > > > > > > Rob Lister wrote: > >> Hi, >> >> Wonder if anyone can help with a small issue I'm having, trying to >> understand how an ALIAS gets resolved. >> >> We are installing a product on a zOS system that utilises MQ to pass >> messages to/from a DB2 Subsystem. >> When we asked the client for certain MQ dataset names, they came back with >> >> SYS5.MQ.XXXX.whatever >> >> saying that the XXXX was using an ALIAS to determine which version was >> being used. Therefore, we wouldn't need to change the dataset names when/if >> we used a new version. >> >> Could anyone explain how that works or, point me to a manual that could >> explain it. >> >> Many thanks, >> >> Rob >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to [email protected] with the message: GET IBM-MAIN INFO >> Search the archives at http://bama.ua.edu/archives/ibm-main.html >> >> >> > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
