Hey Gary,

Don't feel bad.  Turns out you replied with something useful for ME!  We have 
exactly the same issue you described.  So how did you implement your dataset 
alias solution?  Is it automated?  Can you share some code?

TIA,

Linda Mooney

-------------- Original message -------------- 
From: Gary Green <[email protected]> 

> Boy, do I feel stupid. For some reason I thought the OP asked a different 
> question. 
> 
> Really sorry for the topic drift. :( 
> 
> 
> Gary Green 
> Never use a 2x4 when a 2x6 will do just as well! 
> 
> -----Original Message----- 
> From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
> Of Gary Green 
> Sent: Thursday, January 22, 2009 6:47 PM 
> To: [email protected] 
> Subject: Re: Resolving an ALIAS 
> 
> I use aliases all the time with the spin-off SMF files, especially the 
> monthlies. 
> 
> I/we create at least ten different daily and monthly SMF data files (we feed 
> SMF data to other areas), I noticed that some of the other areas that use 
> the monthly files, sometimes run the same file through their software more 
> than a few times. Turns out they forgot which GDG version number 
> represented which monthly tape. I did that myself on occasion. It's even 
> more of a pain when processing daily files... Monday the input is, say..., 
> (-1), but on Tuesday it's (-2) and so. Same thing with the monthly files, 
> especially around the end of the month. 
> 
> So, in our daily SMF processing cycle, every GDG that we create is also 
> assigned a statically named alias. For example..., SMF.MONTHLY.G0011V00 is 
> SMF.SYSTEM.DATA.JAN2008 and the same convention is used for daily files. 
> Best thing about this method is when the base file goes away, i.e. the GDG, 
> the alias goes away with it. 
> 
> It works great. 
> 
> 
> Gary Green 
> Never use a 2x4 when a 2x6 will do just as well! 
> 
> -----Original Message----- 
> From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
> Of Rob Lister 
> Sent: Thursday, January 22, 2009 5:36 PM 
> To: [email protected] 
> Subject: Resolving an ALIAS 
> 
> 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 

----------------------------------------------------------------------
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

Reply via email to