|
Yes, that is correct. When OS400 creates a job (interactive logon, SBMJOB, TFRJOB, etc), OS400 creates a QTEMP (empty) which is accessible ONLY to that job. This space is persistant for the life of the job. Once the job terminates, OS400 destroys that jobs QTEMP and any objects that it contains. Eric DeLong Sally Beauty Company MIS-Project Manager (BSG) 940-898-7863 or ext. 1863 -----Original Message----- From: fkany@averittexpress.com [mailto:fkany@averittexpress.com] Sent: Monday, February 03, 2003 4:40 PM To: Midrange Systems Technical Discussion Subject: RE: SBMJOB CMD(CLRPFM FILE(my_file)) In a CL program submitted to batch, If I were to create a duplicate object of a file in QTEMP, that file can only be used by that job? "DeLong, Eric" <EDeLong@Sallybeauty.com>@midrange.com on 02/03/2003 04:22:39 PM Please respond to Midrange Systems Technical Discussion <midrange-l@midrange.com> Sent by: midrange-l-bounces@midrange.com To: "'Midrange Systems Technical Discussion'" <midrange-l@midrange.com> cc: Subject: RE: SBMJOB CMD(CLRPFM FILE(my_file)) Frank, If your intent is to delete a file in a job's QTEMP library by submitting a NEW job, then this will never work...... Every job has its own QTEMP library. You cannot (easily) access a job's QTEMP from another job. Eric DeLong Sally Beauty Company MIS-Project Manager (BSG) 940-898-7863 or ext. 1863 -----Original Message----- From: fkany@averittexpress.com [mailto:fkany@averittexpress.com] Sent: Monday, February 03, 2003 4:09 PM To: Midrange Systems Technical Discussion Subject: RE: SBMJOB CMD(CLRPFM FILE(my_file)) Rob, Actually, that's exactly what I'm doing. I know it's probably not the "right" way to do it, but it's a long story as to why I'm doing it. Thanks, Frank <big snip> Rob said: Forgive the stupid question, but you aren't submitting a job to clear a file in the library QTEMP are you? Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com 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@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com 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.