× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



On Mon, 23 Apr 2012 14:31:05 +0000
"Stone, Joel" <Joel.Stone@xxxxxxxxxx> wrote:
Would like to create a temp IFS dir to build email text for sending, and would like the system to handle ensuring unique IFS work area for each job. Also delete at EOJ.

How can this be handled so multiple jobs don't build in same IFS area? Use job name? Or is there something like QTEMP for IFS?

Thanks!

If you don't need a directory structure, you can copy your IFS files to QTEMP library as objects type *USRSPC. Their IFS name will be as
/QSYS.LIB/QTEMP.LIB/mymailfile.USRSPC.
But it is possible CCSID problems, so, use CL CPY command with correct FROMCODPAG and TOCODEPAGE parameter values.
Wishes


______________________________________________________________________
This outbound email has been scanned for all viruses by the MessageLabs Skyscan service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
--
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 thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.