|
Sorry Dave - I'm not following your response here. A program run in QINTER does NOT create another job. Its run under you QINTER job, therefore when the program finishes, your QINTER job has not finished, therefore any files created in QTEMP are NOT automatically deleted. They stay there until the user signs off. At least they do at this shop and the other shops I've worked in. Alan Shore NBTY, Inc (631) 244-2000 ext. 5019 AShore@xxxxxxxx midrange-l-bounces@xxxxxxxxxxxx wrote on 01/12/2007 11:53:38 AM:
Right. Correct. Yes. Understood. No change in logic. When the job has completed QTEMP is cleared. Interactive or batch, when the job has completed QTEMP is cleared. IF you are using QTEMP for non-standard purposes, you have to know about it and make sure you have cleaned up after yourself, but that rule applies in any and all circumstances... -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Shore Sent: Friday, January 12, 2007 10:47 AM To: Midrange Systems Technical Discussion Subject: RE: Creating a physical AND Logical file Dave - if you are signed on and run jobs interactively, your signon session is the job. QTEMP assigned to that job is NOT cleared until you signoff. Signing off is when your "job" ends. Alan Shore NBTY, Inc (631) 244-2000 ext. 5019 AShore@xxxxxxxx midrange-l-bounces+alanshore=nbty.com@xxxxxxxxxxxx wrote on 01/12/2007 11:32:25 AM:Sorry, that doesn't make any sense: "clear QTEMP once your job has completed". QTEMP is automatically cleared once your job has completed... ??? -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Wayne McAlpine Sent: Friday, January 12, 2007 10:29 AM To: midrange-l@xxxxxxxxxxxx Subject: Re: Creating a physical AND Logical file I agree. It also makes good sense to clear QTEMP once your job has completed. One thing that has not been mentioned is that if you run the job in batch, there is no possibility of the files stepping on each other. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailinglistTo post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.-- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.