The PASCAL compiler on the RS/6000 (with AIX) allowed the
file names to be specified by the use of environment variables.
IIRC: if you had environment variables that matched the names
in your program statement, that is
program anyname (FILE1, FILE2, FILE3);
you could specify the final file
Just an idea:
if this was possible on today's Linux and C, too,
the migration of mainframe C programs to Linux,
which open files using dd:somename
would be much easier.
( I have this problem sometimes, because management
decides that some of our mainframe based test supporting
C programs should
In 5850145882131277.wa.paulgboulderaim@listserv.ua.edu, on
11/07/2013
at 12:27 PM, Paul Gilmartin paulgboul...@aim.com said:
That doesn't make sense. Rather, I anticipate breathlessly the
advent of QPAM. Please!
Due to the NIH syndrome, VPAM and VIPAM cannot be imported from TSS.
In 1383859615.90107.yahoomail...@web181005.mail.ne1.yahoo.com, on
11/07/2013
at 01:26 PM, Jon Perryman jperr...@pacbell.net said:
I don't see acronyms in different industries a problem. The ones that
get me are within IBM's own website. I can't remember specific's.
Configuration Data Set
In 7701653492190617.wa.paulgboulderaim@listserv.ua.edu, on
11/07/2013
at 02:04 PM, Paul Gilmartin paulgboul...@aim.com said:
When I said a couple weeks ago that alternate DDNAMES should be
handled by ATTACH, transparent to the application, someone asked,
What about programs that scan the
applicable to 99%+ of all serialization scenarios you encounter
To be frank, you might not have very complex serialization requirements.
Also, using PLO when CS,CSG,CDS,CDSG would do is a significant waste of
cycles. For the cases I have seen within our code, uses of PLO (in the
cases where
I really don't see the big deal with an 0c4 in this scenario (should
happen rarely)
You misunderstood my point. You could use PLO to serialize a chain even if
the areas are released as they are deleted provided you always use PLO
Compare and Load to load the pointers and recovery sets a retry to
On 11/07/2013 12:04 PM, Paul Gilmartin wrote:
On Thu, 7 Nov 2013 10:06:14 -0600, Joel C. Ewing wrote:
I share your celebration of the IF Statement; although I have been bit
on one occasion by a non-intuitive behavior of IF statements as well:
the first EXEC in a JOB is always unconditionally
What do we suppose the intended use cases were for this?
Cheers, Martin
Martin Packer,
zChampion, Principal Systems Investigator,
Worldwide Banking Center of Excellence, IBM
+44-7802-245-584
email: martin_pac...@uk.ibm.com
Twitter / Facebook IDs: MartinPacker
Blog:
On Fri, 8 Nov 2013 10:58:46 +0100, Bernd Oppolzer wrote:
( I have this problem sometimes, because management
decides that some of our mainframe based test supporting
C programs should be moved to Linux 64 on Intel).
For now, the solution is
#ifdef MAINFRAME
fopen /* this way */
#else
On Fri, 8 Nov 2013 09:06:20 -0600, Joel C. Ewing wrote:
... Placement in the JCL (from memory) ...
An IF/THEN/ELSE/ENDIF statement construct can appear anywhere in the
job. However, an IF statement specified before the first EXEC statement
in a job is not evaluated before the first step
-Original Message-
From: Kenneth Wilkerson [mailto:redb...@austin.rr.com]
Sent: Friday, November 08, 2013 8:46 AM
To: 'IBM Mainframe Discussion List'
Subject: RE: Serialization without Enque
I really don't see the big deal with an 0c4 in this scenario (should
happen rarely)
You
shmuel+ibm-m...@patriot.net (Shmuel Metz , Seymour J.) writes:
Due to the NIH syndrome, VPAM and VIPAM cannot be imported from TSS.
However, I can provide you with a subroutine for the functionality of
BLDL, FIND and STOW for QSAM, with a single OPEN for multiple members.
You'd have to refit
On Fri, 8 Nov 2013 15:09:59 +, Martin Packer wrote:
What do we suppose the intended use cases were for this?
I suspect there was no discernible intent. More probably, in my
conjecture, prior to the advent of IF, there was a subroutine to
evaluate the COND parameter and determine whether to
Off of the top of my head, IF statements should be able to check SET parms for
values.
Many other things, surely, but this limitation seems most egregious.
From: John McDowell jmcd...@gmail.com
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Thursday, November 7, 2013
Thank You for your help (all of you) but Peter's statement below does not make
sense to me (maybe because I don't understand something).
The reason that the free queue protocol needs a sequence number is because
even if the header matches, the values that you need to put into your
new element
On Fri, 8 Nov 2013 08:04:51 -0800, Frank Swarbrick wrote:
Off of the top of my head, IF statements should be able to check SET parms for
values.
Many other things, surely, but this limitation seems most egregious.
Again, in my recollection without re-checking the JCL Ref, there's no
such
Hmmm! You're right. It's not the symbolic that is not allowed. It's the
comparison to non-numeric values that is not allowed. Interesting!
This works:
1 //IFTHEN JOB ,'IFTHEN TEST',NOTIFY=SYSUID
IEFC653I SUBSTITUTION JCL - ,'IFTHEN TEST',NOTIFY=DVFJS
2 // SET P1=1
On Thu, 7 Nov 2013 22:36:30 -0800, Jon Perryman wrote:
As for concatenating an MVS dataset before the UNIX file isn't as ironic as it
seem's. This actually occurs more often than you think. The classic example is
specifying a block size on the first dataset that is larger than it's block
size.
On 2013-11-08, at 09:54, Frank Swarbrick wrote:
Hmmm! You're right. It's not the symbolic that is not allowed. It's the
comparison to non-numeric values that is not allowed. Interesting!
...
Is this documented as supported, or is one comparand required
to be a return code? Is it
This specific paragraph from Peter is about FREE QUEUE PROTOCOL. This is
where elements on your chain are no longer needed. Peter recommends not freeing
the element. Instead, you should use a queue of free elements that you reuse
when you need a new element.
Peter's concern is not the
First, I'm not sure why you have chosen PLT as your lock word. It's very
important the lock word resolve to the same REAL address no matter where the
PLO executes. Since you are talking about multiple operations against the same
chain, unless all the processes exist in the same shared program
A storage overlay cannot occur in a properly implemented PLO with a counter
as long as the counter is properly maintained with every process
incrementing it by 1. Even in in a free chain implementation, an improper
PLO sequence can result in a circular or broken chain.
Kenneth
-Original
For concatenating dataset overrides not being ironic. I gave an example the
first DD of a concatenation determining the attributes of the open.
Concatenation is not a requirement but in this instance, it helped because it
allowed AMATERSE to obtain the attributes it needs.
I admit I don't
snip
Sorry, but I don't see sysplex as being tightly coupled. At least that's not
the definition I learned 30 years ago. In many ways, sysplex is the z/OS
implementation of High Availability. Being a specialized implementation, it
could do some nice magic with coupling facilities and so on.
The storage overlay does not pertain to the PLO. It pertains to the entire
element not being immediately removed from any type of use. Just because you
removed the element from the chain does not mean it's not in use somewhere. You
can't even say how long the element may be in use (e.g. task
W dniu 2013-11-08 20:02, Staller, Allan pisze:
snip
Sorry, but I don't see sysplex as being tightly coupled. At least that's not
the definition I learned 30 years ago. In many ways, sysplex is the z/OS implementation
of High Availability. Being a specialized implementation, it could do some
Jon Perryman wrote:
begin extract
This is where elements on your chain are no longer needed. Peter
recommends not freeing the element. Instead, you should use a queue of
free elements that you reuse when you need a new , , ,
/end extract
and I have two comments.
First, 'queue of free elements'
Yes, I was talking about all references using PLO. I was also assuming this
was a work queue where deletion from the chain was the methodology for
claiming ownership of the element. However, any serialization method that
performs deletion must also have a method for claiming ownership before an
Beware the $GB limit for non-exteneded format VSAM. Extended format VSAM is
supported for DFHSM CDS's
CA-RECLAIM is enabled in 2 places. Globally IN IGDSMS00, and locally in the
SCLASS/SGROUP(?) definition.
You can turn on CA-RECLAIM for a subset of your storage.
HTH,
snip
We have an hsm
Who frees what is always important. In general a list manager should
have no notion and make no assumptions about the structure or
organization of the things it puts into and removes from the list.
I tell my students that they should think of these things as SOTs,
instances of Something Out
On Fri, 8 Nov 2013 10:49:15 -0800, Jon Perryman wrote:
... IBM modified IEBGENER (and other utilities) to support DCB for UNIX files
so yes they do work.
I strongly doubt that although I haven't access to the source code to verify it.
Rather, I understand that the support was entirely in the
Folks:
I have done support for automated JCL management tools for the past 30+ years
and it is amazing the number of features in JCL that are not documented in
the IBM JCL reference manual. It was difficult dealing with clients who would
tell us they had coded something in their JCL, yet
On 8/11/2013 09:51 AM, John Gilmore wrote:
About QDAM, I should perhaps have made it clearer that my student was
having me on.
John Gilmore, Ashland, MA 01721 - USA
John,
You disappointed me. I fully expected that you would assigned the
student the task of writing the functional specs, in
On Fri, 8 Nov 2013 16:07:37 -0500, Mitch wrote:
I have done support for automated JCL management tools for the past 30+ years
and it is amazing the number of features in JCL that are not documented in
the IBM JCL reference manual. It was difficult dealing with clients who would
tell us they
I'm guessing that Peter was warning against the situation where you have an
element table rather than a queue. Queues are straight forward because each
entry will only be in use by 1 program at any given time (ownership is always
the task using it). Element tables on the other hand may have
Paul:
You are exactly right. That is what IBM would tell us as a vendor, but then we
had to turn around and support our customers because it was an undocumented
feature of the IBM JCL processing environment. Made new releases of both our
product and operating systems upgrades from IBM all
I remember that clearly, and I believe Mitch and I are referring to the same
ISV (I know we both worked there, but at different times). We had a developer
encounter behavior in the JCL that differed from the documentation, and he
reported it to IBM. IBM fixed it so that it agreed with the doc,
Looks like my impossible with respect to the free queue protocol needed
to be qualified by until PLO came along as long as you have storage to
work with for the PLO parameters.
As was pointed out to me,
PLO CL and PLO DCS can be used to implement the free queue protocol (and
not need the
I suspect that you are correct that the I/O macro's have some sort of DCB
support built in rather than changing IEBGENER. IBM specifically states that
UNIX files are supported in some way in BSAM, QSAM, BPAM, and VSAM. It also
says that certain macro's have restrictions and incompatibilities
Rich:
DSSI?
Mitch
-Original Message-
From: Rich Way rich@voltage.com
To: IBM-MAIN IBM-MAIN@LISTSERV.UA.EDU
Sent: Fri, Nov 8, 2013 2:22 pm
Subject: Re: JCL
I remember that clearly, and I believe Mitch and I are referring to the same
ISV
I know we both worked there, but at
Yup.
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of
Mitch [mitc...@aol.com]
Sent: Friday, November 08, 2013 3:28 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: JCL
Rich:
DSSI?
Mitch
-Original Message-
From: Rich Way
Please consider forwarding this invitation to other System z professionals that
could benefit from the ongoing no charge Series z education and networking
opportunities. This could include but not limited to Applications, Auditing,
Automation, Capacity Planning, Contingency Planning, Network,
43 matches
Mail list logo
