Re: DIR QNTC\ /b /ad > *some file that can be read in CL or RPG*

Have you tried for instance (it occurs to me, i have not tried it):
DIR QNTC\ /b /ad > /QSYS.LIB./SOMELIB.LIB/SOMEFILE.FILE/SOMEMBR.MBR

Not sure if it should be /QNTC\. If you get something as above, then I
guess it's OK.

JS

El jue, 12 dic 2024 a las 22:26, Dan Bale (<dan.bale@xxxxxxxxxxxxxxxxxxxxx>)
escribió:

So here's the deal. We find that some links in QNTC disappear after an
IPL. Currently, we capture the links before IPL via:
DSPLNK OBJ('/QNTC/*') OUTPUT(*PRINT) OBJTYPE(*ALLDIR) DETAIL(*NAME)
DSPOPT(*ALL)

Then, after IPL, using the DSPLNK report, if we find any links are
missing, we manually recreate them via CRTDIR.

The problem arises when some links have a trailing blank in the name. I
don't know how or why, but they do, and we have to "deal with it". I
discovered this by opening a command window, changing to the drive which is
mapped to the IFS, then using:
DIR QNTC\ /b /ad > \DirQNTC.txt

When I open DirQNTC.txt in Notepad++, it will show any trailing blanks
before the CR/LF.

Unfortunately, there's no way to tell if there are any trailing blanks on
the DSPLNK report.

I am trying to automate the collection of the QNTC links with the trailing
blanks into a table on the i, so we can recreate them easily when needed.
My thought is to do:
DIR QNTC\ /b /ad > *some file that can be read in CL or RPG*
but am drawing blanks on how to do this, if it's even possible. Any ideas
on how to accomplish this?
*** CONFIDENTIALITY NOTICE: The information contained in this
communication may be confidential, and is intended only for the use of the
recipients named above. If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination, distribution, or
copying of this communication, or any of its contents, is strictly
prohibited. If you have received this communication in error, please return
it to the sender immediately and delete the original message and any copy
of it from your computer system. If you have any questions concerning this
message, please contact the sender. ***
--
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.