On Sun, 30 Apr 2017 10:32:50 -0400, Steve Thompson wrote:
> ...
>Example: iea2b6a0.pdf might become iea2b6a0_JCL_REF.pdf
> ...
>Now, on a Linux system I can create a link to that particular
>manual so that it becomes JCL_REF.pdf, but this takes a while to
>do for each manual that I'm interested in. But that's me, how
>many are you interested in?
>
A script could process the index.html file to generate all the links.
>And if one is a Windows user, can one easily do a link?
>
Lately, Windows has a "mklink" command:
o Requires admin authority. WTF!?
o Must specify whether the link is to a document or to a folder. WTF!?
... or just use Cygwin and a file manager such as Thunar.
I just use the index.html file in a browser.
>Notice, I have these manuals in sub directories by O/S release
>(yes, I also do this for VM as well) so that I can find something
>that I know is specific to a certain version/release.
>
I've done this, not for manuals but for listings. Two directory hierarchies:
./name/version -> document
./version/name -> document
... works pretty well browsing with ISPF 3.17.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
