RE: Odd error - QSH ajar command -- MIDRANGE-L

I have no problem with shell scripting. Used to admin and do some app development for a dozen ATT System V and, later, AIX boxes.

My mind just doesn't go there anymore when the primary process is CL/RPG/DB2. I just tend to think to fork a QSH command. Plus, sadly, I have to think about someone else in my dept possibly dealing with it down the road. <big frown>.

Yeah, I have Python too - invoked from a CL launched by Robot.

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Jack Woehr
Sent: Friday, August 02, 2019 9:25 PM
To: Midrange Systems Technical Discussion
Subject: Re: Odd error - QSH ajar command

It's easy to launch a shell script from a CL.

I'm doing everything in Python scripts these days, launched from CLs, often
from the job scheduler.

It's easier than what we've been doing for decades. You just have to master:

- coding in Python or shell scripts
- learning to call classic commands and programs from inside PASE Python
or Bash
- learning how to write to a db from that env

It's all pretty simple. It all works.

Once you've made the leap it you won't go back, because it's easier and
everything left that's alive and growing in IBM i is either Db2 code or
PASE programming.

On Fri, Aug 2, 2019 at 9:42 PM Roger Harman <roger.harman@xxxxxxxxxxx>
wrote:

Originally, I was using jar and piping the file list into it. That gave
me some issues with a huge file list. So, I switched to using xargs to
parcel out the file list. Can't recall why I switched to ajar at the same
time though - I could just use the "u" option on jar.

So, launch QSH to launch a shell script?

"All problems in computer science can be solved by another level of
indirection, except for the problem of too many layers of indirection."

I'll have to do some more experimenting.

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf
Of Jack Woehr
Sent: Friday, August 02, 2019 4:37 PM
To: Midrange Systems Technical Discussion
Subject: Re: Odd error - QSH ajar command

Write a bash shell script in the IFS under PASE using open source zip and
launch it from a CL.

On Fri, Aug 2, 2019 at 3:35 PM Roger Harman <roger.harman@xxxxxxxxxxx>
wrote:

V7.2

I have a CL looping through a list of wildcards and building a zip file
using ajar. The build first creates an empty shell zip and then loops
through the wildcards adding to the zip.

In batch, I'm regularly seeing this error:
ajar: Could not rename temp file `<my zipfile>.zip_<some random
identifier>' to `<my zipfile>.zip
(Warning) Could not remove temp file `<my zipfile>.zip_<some random
identifier>'.

Running the same process interactively works fine. I came across a note
that said to be sure the environment variable QIBM_MULTI_THREADED was set
to Y and I've added that to my Robot job stream - it was not in my
interactive job though (WrkEnvVar).

Batch job is running from Robot and the user profile is on the AUTL for
the ifs folders (as am I).

Any thoughts? Thanks!

Roger Harman
COMMON Certified Application Developer - ILE RPG on IBM i on Power

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
Jack Woehr
Absolute Performance, Inc.
12303 Airport Way, Suite 100
Broomfield, CO 80021

NON-DISCLOSURE NOTICE: This communication including any and all
attachments is for the intended recipient(s) only and may contain
confidential and privileged information. If you are not the intended
recipient of this communication, any disclosure, copying further
distribution or use of this communication is prohibited. If you received
this communication in error, please contact the sender and delete/destroy
all copies of this communication immediately.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com