We have a similar issue with QTEMP and a managed file transfer product. We wanted to give it access to a workfile which would usually be in QTEMP.
The solution we used was to create a real library ZZQTEMP (or whatever) that is NOT in any library list. Make a unique name (typically using job #) and place objects there. We call it our "Global" Qtemp and pass the name into the MFT process. You just have to cleanup after yourself.
Same principle for IFS work files - create a subdirectory under /tmp for the job and pass that name to the MFT product or, in your case, the QSH command.
Roger HarmanCOMMON Certified Application Developer – ILE RPG on IBM i on PowerOCEAN User Group – Vice-President, Membership (2014)
This mailing list archive is Copyright 1997-2019 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