I've got a few JES2 questions that I'm a little confused about.
- For punches... how come destinations have to be explicitly defined with a DESTID statement before using them on a ROUTECDE, as compared to a printer where you could just put anything onto a ROUTECDE for that without any sort of pre-definition for it?
- Is there any reason that a punch and a reader can't be dynamically defined to JES2? Would you really have to re-IPL each time you wanted to add new ones to the system?
- Going back to my first question... Say that I have the following definitions in my JES2PARM.
Normally, you would expect PUN1 to take LCLP01, PUN2 to take LCLP02, and PUN3 to take LCLP03. Now, say that I run the following command:
PUN1 now takes work routed for LCLP02 - but this makes no sense, as the DEST for DESTID(LCLP02) is stated to be PUN2. Now this further complicates things because it makes it seem useless/unnecessary now, but if I just use DEST=LOCAL for the DESTID, no punch selects it at all, and the destination for the job just changes to LOCAL (as opposed to saying/staying as LCLP02). So why is this, and again, what's the point?
- Assuming that there really is a point to all of this, why don't we have to use this for printers, and when should we use it for printers?
Sorry if these seem like basic questions - I do understand what I need to do to make it work, but my question is just more of a "Why do we need to do it this way to make it work?"
Thanks for any insight into this!