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



Scott,

We're on V6.1, so I figured the fix was already in the OS. I'll work
with this a bit more next week, and once I'm convinced it isn't me
I'll call IBM to get the 6.1 PTF nbr.

I'm just starting with shell scripting. Not sure why I was drawn to
QP2SHELL instead of QSHELL - I think it was because of not starting
other jobs.

Why should I use qshell over qp2shell? I don't know enough about them
to understand what the differences mean.

Is it possible for the error to propagate? I want to keep this as
simple as possible because once I'm done with it, I don't want to be
the only one who can support it. Been there, done that! So I
switched gears and started looking at creating an sftp script file on
the fly, and then calling sftp with qshell instead of qp2shell.

Phil

On Fri, Aug 20, 2010 at 4:38 PM, Scott Klement
<midrange-l@xxxxxxxxxxxxxxxx> wrote: o
Hi Phil,

Do you have the PTF installed that fixes error handling?

You're right that QUSRJOBI (which, IMHO, you should not be using.. you
should be using QShell!) won't return failure...   but that's because
your script doesn't propagate the error to the caller.

But the fact that the RENAME runs even if the PUT failed implies to me
that you're missing the PTF.  Without that PTF, you're going nowhere fast.

For v5r3, the PTF is SI25208
For v5r4, the PTF is SI25209




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.