Sorry about the formatting in this text only newsgroup. However, you
can see it formatted correctly in the Jol Reference Guide at
http://members.ozemail.com.au/~oscarptyltd/Jol_Reference_Guide.pdf.
That said, there is a special command in Jol for storing or saving
symbolic variables for reuse. The command saves it in a format that can
be read again by the Jol translator/compiler. But it could be easily
modified to save them as GBLS for Assembler, for example.
And so if I was using Jol and wanted to save the symbolics for later
use, I could use the:
SAVESYMS - Immediate Command
Purpose
The *SAVESYMS* command stores specified symbolic values into a member of
a partitioned data set. These symbolic values may be INCLUDEd in a
subsequent compile, thus providing the facility to communicate with
other Jol procedures, or the same procedure at a later time.
Format:
SAVESYMS symbolic1 [,symbolic2 ...]
IN
'data-set-name(member)' ;
where
symbolic-variable-name-list
is a symbolic name or a list of names separated by commas, without the
*%* preceding them.
data-set-name
specifies the name of an *existing* data set or library into which the
data will be saved.
Details
Any *symbolic variable* that has been used during the current
compilation may be saved in an external data set. Subsequent runs can
reuse the saved or previous values in issuing an *INCLUDE* specifying
the member name the symbolics were saved in.
By displaying these values, perhaps in a *PANEL*, the user will
automatically know the data that was used for the prior run. The values
saved may then be used on a subsequent run to initialize values to those
that were set on a previous run.
Notes
The data is stored as a series or Symbolic Variable Assignments. Thus:
SAVESYMS DAY IN '%SYSUID.JOL(X)';
will result in member *X* containing a statement similar to:
%DAY='MONDAY';
To retrieve the data, simply *INCLUDE* the member(s).
The information can also be used by another job, and so information may
be passed from job to job.
If subsequent saves are made to the same data set or member, the new
data will destroy the data that was previously saved.
To retain the previous data, you must copy it to a different data set,
or use a different member name. For example:
SAVESYMS RUN,DOLLVAL IN '%SYSUID.JOL(%DAY)';
will automatically save the data for symbolic variables *RUN* and
*DOLLVAL* in the Jol data set, but the member name will change depending
on the day the job is used.
Example
SAVESYMS A,B IN '%SYSUID.JOL(LASTRUN)';
will save the values of *A* and *B* in the users private Jol data set in
the member called *LASTRUN*.
To retrieve the data that was saved, issue the following:-
INCLUDE LASTRUN;
----------------------------------------------------------------------
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
