It is useful to be able to receive the "second" generation before processing 
the "first".  It is less useful that if this happens you have to make a JCL 
change to be able to process the older generation once a newer generation has 
been created.

Are there standard ways of dealing with this?

Signed, new MVS person.
-- 

Frank Swarbrick
Applications Architect - Mainframe Applications Development
FirstBank Data Corporation - Lakewood, CO  USA
P: 303-235-1403


On 5/7/2010 at 10:35 AM, in message
<of44bcf0ca.bf9d8380-on8525771c.005ac0f2-8525771c.005b3...@tsys.com>, Kirk
Talman <[email protected]> wrote:
> IBM Mainframe Discussion List <[email protected]> wrote on 05/06/2010 
> 04:34:31 PM:
> 
>> From: Patrick Lyon <[email protected]>
> 
>> >And when talking to Unix/Windows folks, explaining (over and over)
>> >that dataset nodes are not directory paths and that PDS(E) can only be
>> >1 level deep.
>> >
>> >As well as they way GDGs work (unless they have a VAX background).
>> 
>> You'll have to excuse them.  They only understand what they call "modern 
> 
>> technology".
> 
> "You didn't send us a file yesterday/x hrs ago."
> 
> Explain to a customer that if they want to have more than one transmission 
> to a file on their squatty box in a given time period, they must process 
> that file before the next transmission.  Or they can pay for multiple 
> transmission setups.  Or the file will be overlaid.
> 
> The semantic problem is most of us experience new as more complicated than 
> old.  But modern does not equal more capable.
> 
> -----------------------------------------
> The information contained in this communication (including any
> attachments hereto) is confidential and is intended solely for the
> personal and confidential use of the individual or entity to whom
> it is addressed. If the reader of this message is not the intended
> recipient or an agent responsible for delivering it to the intended
> recipient, you are hereby notified that you have received this
> communication in error and that any review, dissemination, copying,
> or unauthorized use of this information, or the taking of any
> action in reliance on the contents of this information is strictly
> prohibited. If you have received this communication in error,
> please notify us immediately by e-mail, and delete the original
> message. Thank you 
> 
> ----------------------------------------------------------------------
> 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

>>> 

The information contained in this electronic communication and any document 
attached hereto or transmitted herewith is confidential and intended for the 
exclusive use of the individual or entity named above.  If the reader of this 
message is not the intended recipient or the employee or agent responsible for 
delivering it to the intended recipient, you are hereby notified that any 
examination, use, dissemination, distribution or copying of this communication 
or any part thereof is strictly prohibited.  If you have received this 
communication in error, please immediately notify the sender by reply e-mail 
and destroy this communication.  Thank you.

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