On Mon, 27 Mar 1995, Williams, Pete - Prog Analyst wrote:
> having is that I need to get rid of the original data file after it has been
> copied to the new group and account.
 
> The monitoring job is signing on as the manager of the initial account, and
> has SM, AM, and OP capabilities.  Unfortunately, it is not the same user and
 
> Does anyone have any wonderful ideas?  Please, I beg of you, do not tell me
> to just use MPEX.  I know how good it is, but management doesn't seem to
 
Dare I mention the GOD utility that comes with that product you don't
want me to tell you about?  <<grin>>
 
If I were in the position that:
 
1.  The copying job cannot get SM capability (if it could, it could purge
the file regardless of creator).
 
2.  The monitor DOES have SM, so it could purge the file if only it knew.
 
3.  And I had a nice message file hanging around
 
4.  And the monitor 'owned' the message file and had 'released' it so
anybody on the system could write a message.
 
5.  And all the jobs that copied files knew about the message file and
would write the name of the file after they copied it.
 
Then,
I'd hang a no-wait IO on the message file (so I could do other stuff
while waiting for a file name to purge) and would then purge the file
mentioned in the message file whenever the READ did complete.  Of course,
if I was allowed to have a second monitor up and running (a second job
unless I had MPEX to help me do multi-processes running in the same job)
or I wanted to issue a CREATEPROCESS intrinsic call, then I wouldn't use
NO-WAIT IO and would simply read until the file was empty.  One trick is
needed.  Turn on extended waits so you don't get an EOF because no-one is
writing to the file.  You will need to have a writer that writes a
particular 'message' that your program will interpret as beeing 'SHUTDOWN
TIME' message.
 
Of course, I'd explain to management that this will cost about $6000 to
write and maintain over the next year and that the cost for owning MPEX
is X.  I'd make sure that $6000 was bigger than X.  That NO-WAIT IO on a
KSAM file with EXTENDED WAITS sounds like a lot of work.
 
--Steve
 
PS.  Of course, I could also just have the copy jobs stream a sub-job
after they have copied the file.  This sub job will log on as the Account
Manager of the source file and issue a purge.  I presume the monitor is
creating the JCL that copies the file and it could write the additional
lines of JCL?
 
 
+----------------------------------------------------+
| Steve Butler          Voice:  206-464-2998         |
| The Seattle Times       Fax:  206-382-8898         |
| PO Box 70          Internet:  [log in to unmask] |
| Seattle, WA 98111    Packet:  [log in to unmask]       |
+----------------------------------------------------+
All standard and non-standard disclaimers apply.
All other sources are annonymous.