Re: qsh stdout difference per IBM i

I'd try it but I'm trying to avoid VPNing into work as I don't want to
show as available on our IM. 😊
I wonder if one of the directories might be a symbolic link?
I'm also concerned why the one shows the full path name. Check both your
*SYS and *JOB environment variables.
Are they on the same version of the OS? Simple outputs like this are
almost always covered with a generic statement in the MTU as a way of
encouraging you to use APIs or SQL services instead of relying upon
positioning in spool files, etc.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 7310 Innovation Blvd, Suite 104
Ft. Wayne, IN 46818
Ship to: 7310 Innovation Blvd, Dock 9C
Ft. Wayne, IN 46818
http://www.dekko.com

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Jay
Vaughn
Sent: Friday, April 15, 2022 2:56 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: qsh stdout difference per IBM i

CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you recognize the sender and know
the content is safe.


I'm trying to figure out why 2 different IBM i's produce different stdout
outputs...

system1
OVRDBF FILE(STDOUT) TOFILE(QTEMP/DIRLIST)
OVRSCOPE(*JOB)
OPNSCOPE(*JOB)

qsh cmd('ls -A /home/jvaughn/.ssh')

SRCSEQ SRCDAT SRCDTA
.00 0 xyz_rsa_prv
.00 0 xyz_rsa_pub
.00 0 abc_rsa_prv
.00 0 abc_S_rsa_pub
******** End of data ********

output nicely per row in qtemp/dirlist

system 2
same steps above but...

SRCSEQ SRCDAT SRCDTA

.00 0 /home/jvaughn/.ssh/STOREPORT_rsa_pub
/home/jvaughn/.ssh/i
.00 0 /home/jvaughn/.ssh/id_rsa
/home/jvaughn/.ssh/known_h
******** End of data ********

2 files per row instead of 1...

tia

Jay
--
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@xxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

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