On Thu, 29 Jan 2009 15:36:19 -0600, Frank Swarbrick wrote:
On Thu, 29 Jan 2009 13:53:45 -0600, Tom Marchant wrote:
Maybe. If the gener abends, the XMIT group will be kept. If it fails with
a non-zero return code, they will be deleted.
Thanks for the warning. I tested it out by forcing an out
On Fri, 30 Jan 2009 07:12:46 -0600, Tom Marchant m42tom-
ibmm...@yahoo.com wrote:
On Thu, 29 Jan 2009 15:36:19 -0600, Frank Swarbrick wrote:
On Thu, 29 Jan 2009 13:53:45 -0600, Tom Marchant wrote:
Maybe. If the gener abends, the XMIT group will be kept. If it fails with
a non-zero return
-snip--
Tom Marchant wrote:
On Thu, 29 Jan 2009 15:36:19 -0600, Frank Swarbrick wrote:
On Thu, 29 Jan 2009 13:53:45 -0600, Tom Marchant wrote:
Maybe. If the gener abends, the XMIT group will be kept. If it fails with
a
First I want to thank everyone for all of their ideas. After due
consideration,
here is what I think we'll end up doing.
I'm going to create two GDG datasets:
/* IDCAMS COMMAND */
DEFINE GENERATIONDATAGROUP -
(NAME(PROD.XMIT.TXNFILE) -
LIMIT(6) -
)
On Thu, 29 Jan 2009 12:35:37 -0600, Frank Swarbrick fswarbr...@gmail.com
wrote:
First I want to thank everyone for all of their ideas. After due
consideration,
here is what I think we'll end up doing.
I'm going to create two GDG datasets:
/* IDCAMS COMMAND */
DEFINE GENERATIONDATAGROUP -
On Thu, 29 Jan 2009 12:35:37 -0600, Frank Swarbrick wrote:
On a business day we'll have two jobs. The first one will look very much like
this:
//GDGTST3A JOB NOTIFY=SYSUID,MSGCLASS=X,CLASS=A
//BACKUP EXEC PGM=IEBGENER
//SYSUT1 DD DISP=(OLD,DELETE,KEEP),DSN=PROD.XMIT.TXNFILE
//SYSUT2 DD
On Thu, 29 Jan 2009 13:53:45 -0600, Tom Marchant m42tom-
ibmm...@yahoo.com wrote:
On Thu, 29 Jan 2009 12:35:37 -0600, Frank Swarbrick wrote:
On a business day we'll have two jobs. The first one will look very much like
this:
//GDGTST3A JOB NOTIFY=SYSUID,MSGCLASS=X,CLASS=A
//BACKUP EXEC
On Thu, 29 Jan 2009 13:53:45 -0600, Tom Marchant m42tom-ibmm...@yahoo.com
wrote:
On Thu, 29 Jan 2009 12:35:37 -0600, Frank Swarbrick wrote:
On a business day we'll have two jobs. The first one will look very much like
this:
//GDGTST3A JOB NOTIFY=SYSUID,MSGCLASS=X,CLASS=A
//BACKUP EXEC
Hello,
This might run into trouble if you need to open lots of datasets due to
holidays.
Suppose, your program always defines the last 3 datasets (0), (-1) and
(-2) with the corresponding DD statements in your JCL.
However, you'll have some program logic to determine what day of the
week it is.
: New GDG question
Hello,
This might run into trouble if you need to open lots of datasets due to
holidays.
Suppose, your program always defines the last 3 datasets (0), (-1) and
(-2) with the corresponding DD statements in your JCL.
However, you'll have some program logic to determine what day
Frank,
You have received several suggestions on this. Here's one more that we
do with data that we get from our parent company. If you have access to
somebody who can make a minor modification to the FTP send commands on
the other end, you could have them simply change their FTP commands to
do
One easy way is for the daily job to process all generations of the
dataset, then delete them when it's captured the data.
There are variations on that theme using that would involve copying the
FTP generations to a workday generation if you need to keep the input.
One thing I've learned,
Well, this may be a bit too clever But it works flawlessly for me.
At 1 second past midnight, I run some REXX which produces a series of JCL
SET SYMBOL statements and stores these statements in a production JCL
Procedure library. (send me a PM and I'll send you an example of what JCL
this
I have several possible solutions for you, some free some not.
1) The company I work for markets a product called SyzAuto which allows you
to schedule JOBs (or tasks or commands) based on Day of Week, Month, and
various frequencies) with IF logic etc. Most job scheduling systems allow
for this
I've handled this scenerio in the past by having the ftp write to a non-gds
dsn.
Then have the transfer trigger an IEBGENER that concatenates (0) gen with
the non-gds to create (+1) gen.
This can then run any number of times until the business day processes the
files by just calling the (0) gen
15 matches
Mail list logo
