Exactly right.  That's why symbol resolution belongs only in the execution
environment, not in conversion or interpretation.  When and where the JCL
executes is the only time and place that count, so that is where and when
the symbols should be resolved.

And no, I can't have my symbolics resolved in my application without a
boatload of trouble with dynamic allocation and the restricted length of
PARM input and lots of other stuff.  It belongs in JCL, not in my
application.  Perhaps you don't have to deal with batch applications with
100+ DD statements?  I do.

OTOH, &SYSUID certainly ought to reflect the TSO userid of the actual
submitter from the actual submitting system, and that isn't necessarily the
executing system.  There's a case where the value should arguably be set at
submission time, not any of Conversion or Interpretation or Execution.

I can also see that "resource predicting" systems might have a little
problem with this approach, since they try to manage what will run and where
based on what resources are used.  If any resource names use symbolics, the
managing system has to know what the symbols *will* resolve to when
execution finally is permitted to proceed.  I can see where that might be a
place where symbols would need to be forbidden.  That's an implementation
restriction, though, not a design flaw.

And quite frankly, if &TIME and &DATE are the issue, leave them out for now
and give us the rest.  I'll admit they would be quite useful, but we have
lived without them for this long, we can probably wait some more.

Peter 

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] 
Sent: Thursday, December 01, 2005 3:35 PM
To: [email protected]
Subject: Re: Using symbolic in JCL

On Wed, 30 Nov 2005 13:35:10 -0500, Farley, Peter x23353
<[EMAIL PROTECTED]> wrote:
<Snipped>
Huh?  You can have your symbolics resolution in your application at run
time.  You want the resolution in the JCL to reflect execution time?
That may be weeks after the JCL is processed.  I don't pretend to know what
part of JCL processing is done during Conversion and what during
Interpretation, but I am pretty sure neither process is psychic (even in an
ESP environment).  They can't know what the symbol values will be at
execution.

_
This message and any attachments are intended only for the use of the addressee 
and
may contain information that is privileged and confidential. If the reader of 
the 
message is not the intended recipient or an authorized representative of the
intended recipient, you are hereby notified that any dissemination of this
communication is strictly prohibited. If you have received this communication in
error, please notify us immediately by e-mail and delete the message and any
attachments from your system.

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