× 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.



I have a bash command line process where I am calling a CL command which calls several pase commands via STRQSH from the CL command.

Sequence - bash command calls system which calls CL command which calls qsh/pase. Crash when trying to get environment variable for QSECOFR. Well ya, it should be using my home directory.

The process appears to spawn several sub-processes that show as running under QSECOFR instead of my user, even though the job logs end up in my jobq.

Why would a spawned SSH job by running under QSECOFR instead of my user ID ?

I did check and my SSH server us running as QSECOFR (which I imagine should be changed), however the potential problem remains the same in that the home directory for the SSH server job is picked up on the spawned jobs instead of my user.

This sounds similar to the old QUSER issue we had with IBM i Access ODBC and other background processes.

The issue for me is that the pase calls are picking up home directory info for QSECOFR instead of my user from the home directory.

Very interesting.

Hope this makes sense.

Any thoughts appreciated ?

Thanks

BTW: The CL command process runs fine if I just run from a regular IBM i job.

Regards,
Richard Schoen
Web: http://www.richardschoen.net<http://www.richardschoen.net/>
Email: richard@xxxxxxxxxxxxxxxxx<mailto:richard@xxxxxxxxxxxxxxxxx>
Phn: (612) 315-1745


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.