Re: Manual Naming for Local use [WAS: Issue with SK4T-4949-13 - IBM Online Library....]
On Mon, 1 May 2017 15:34:58 -0500, Joel C. Ewing wrote: > >IBM could make file names of manual files reflect the formal manual >titles, and you could still end up with something difficult to use. > Would it be any worse than the 8.3 names we see nowadays? But yes, the effort could be pretty much doomed by Corporate Standards requiring titles to begin "International Business Machines® (A New York Corporation) Multiple Virtual Storage Data Facility ..." I believe the cross-reference link rot I mentioned earlier is aggravated because the file names change with each revision and might actually be alleviated by stable transparent names such as "JCL Reference.pdf" -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Manual Naming for Local use [WAS: Issue with SK4T-4949-13 - IBM Online Library....]
On 04/30/2017 09:32 AM, Steve Thompson wrote: > More than a year ago (it may have been 2012, I just can't remember), I > put forth an idea that IBM do a search for its manuals based on their > ID for the manuals, while the user could name that manual from that > point. > > Example: iea2b6a0.pdf might become iea2b6a0_JCL_REF.pdf > > This was immediately slapped down as never gonna happen. > > But, what if IBM were to do this naming? > > Should this be put forth as a Share request/requirement? > > 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? > > And if one is a Windows user, can one easily do a link? > > 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. > > Regards, > Steve Thompson > > > On 04/29/2017 08:11 PM, Brian Westerman wrote: >> I rename a few of the manuals (the ones I use all the time), but I >> too wish the file names of the manuals were the full manual name. I >> would hate to think about trying to rename hundreds of manuals each >> time, I would go nuts, but I do copy about 20 of them that I really >> care about. >> >> Using the index is great (I rename that too), but it still would be >> nice to have better names on the individual files. >> >> Brian >> > Be careful what you wish for. Reminds me of the old days with a physical hard copy manual library when we tried to use secretarial types for putting new manuals in folders and labeling the folders. We continually had problems finding things because IBM was terrible about using very long, very explicit manual titles like "Multiple Virtual Storage Data Facility Data Set Services (whatever)", which the help dutifully copied. They either ran out of space before they got to the "whatever" that actually differentiated what the manual was about, or there was so much verbiage the useful part was hard to find. We tried making rules about what parts of titles they could omit or replace with acronyms, but having the technical staff keep that list updated and training others how to use it became almost as much work as filing all the manuals ourselves. it was a continual battle until we were finally able to phase out the hard copy library. IBM could make file names of manual files reflect the formal manual titles, and you could still end up with something difficult to use. -- Joel C. Ewing,Bentonville, AR jcew...@acm.org -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [EXTERNAL] Re: Manual Naming for Local use [WAS: Issue with SK4T-4949-13 - IBM Online Library....]
Colons are not valid in file names on Windows. Slashes aren't valid either, but as they also aren't on Unix, the tool seems to drop them. Backslashes could be a real mess, as they mean completely different things on Unix vs. Windows. sas On Mon, May 1, 2017 at 1:59 PM, Dyck, Lionel B. (TRA)wrote: > Tried it on Windows 10 bash shell and got a LOT of 'invalid argument' > messages on the ln command - but not on all. > > Example: > > ln: failed to create symbolic link ‘zOS_V2R2.0_Communications_ > Server:_IP_Diagnosis_Guide.pdf’: Invalid argument > ln: failed to create symbolic link > ‘zOS_V2R2.0_Communications_Server:_SNA_Messages.pdf’: > Invalid argument > ln: failed to create symbolic link ‘zOS_V2R2.0_Communications_ > Server:_IP_Messages_Volume_1_(EZA).pdf’: Invalid argument > ln: failed to create symbolic link ‘zOS_V2R2.0_Communications_ > Server:_IP_Messages_Volume_2_(EZB,_EZD).pdf’: Invalid argument > > > -- > Lionel B. Dyck > Mainframe Systems Programmer - TRA > Enterprise Operations (Station 200) (005OP6.3.10) > Information and Technology, IT Operations and Services > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [EXTERNAL] Re: Manual Naming for Local use [WAS: Issue with SK4T-4949-13 - IBM Online Library....]
Current (before the "Creators" update) version is Ubuntu 14.04, which only has xpdf v3.03. Xpdf latest version is v3.04, so you may want to wait for the "Creators" update to try again. Or try the Windows binary directly from the foolabs site. My guess is that John M. is probably running the latest Linux version of the xpdf tool. Peter -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Dyck, Lionel B. (TRA) Sent: Monday, May 01, 2017 2:00 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [EXTERNAL] Re: Manual Naming for Local use [WAS: Issue with SK4T-4949-13 - IBM Online Library] Tried it on Windows 10 bash shell and got a LOT of 'invalid argument' messages on the ln command - but not on all. Example: ln: failed to create symbolic link ‘zOS_V2R2.0_Communications_Server:_IP_Diagnosis_Guide.pdf’: Invalid argument ln: failed to create symbolic link ‘zOS_V2R2.0_Communications_Server:_SNA_Messages.pdf’: Invalid argument ln: failed to create symbolic link ‘zOS_V2R2.0_Communications_Server:_IP_Messages_Volume_1_(EZA).pdf’: Invalid argument ln: failed to create symbolic link ‘zOS_V2R2.0_Communications_Server:_IP_Messages_Volume_2_(EZB,_EZD).pdf’: Invalid argument -- Lionel B. Dyck Mainframe Systems Programmer - TRA Enterprise Operations (Station 200) (005OP6.3.10) Information and Technology, IT Operations and Services -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John McKown Sent: Monday, May 01, 2017 12:12 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [EXTERNAL] Re: Manual Naming for Local use [WAS: Issue with SK4T-4949-13 - IBM Online Library] How I do it on Linux is to use the "pdfinfo" program. Example: [tsh009@it-johnmckown-linux Documents]$ pdfinfo dz9zr010.pdf Title: z/Architecture Principles of Operation Subject:z/Architecture Keywords: Author: IBM Corporation Creator:FrameMaker 10.0.2 Producer: Acrobat Distiller 10.1.13 (Windows) CreationDate: Thu Feb 19 17:32:41 2015 CST ModDate:Thu Feb 19 17:32:41 2015 CST Tagged: no UserProperties: no Suspects: no Form: AcroForm JavaScript: no Pages: 1732 Encrypted: no Page size: 612 x 792 pts (letter) Page rot: 0 File size: 15180376 bytes Optimized: yes PDF version:1.6 So for i in *.pdf;do ln -s "${i}" $(pdfinfo "${i}" | awk '$1=="Title:" {print $0;}' | sed -r 's/^Title: *//;s|/||g;s/ +/_/g;').pdf;done -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [EXTERNAL] Re: Manual Naming for Local use [WAS: Issue with SK4T-4949-13 - IBM Online Library....]
Yes, they are there in the Win10 bash shell (or rather they are after you install the xpdf package). The Win 10 bash shell is at Ubuntu level 14.04, which is a few years old now. The new version due to hit Win 10 systems soon as a big update ("Creators" update) will have Ubuntu version 16.04 which is much more recent. IMHO the availability of a genuine bash shell and all the Ubuntu Linux command-line tools is quite an interesting development in the Windows world. Peter -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Dyck, Lionel B. (TRA) Sent: Monday, May 01, 2017 1:57 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [EXTERNAL] Re: Manual Naming for Local use [WAS: Issue with SK4T-4949-13 - IBM Online Library] I found that under Windows 10 bash you can install the package with pdfinfo and it then the command seems to work - I haven't downloaded the zip file yet to try it out but sed, awk, etc. all seem to be in place under the bash shell. -- Lionel B. Dyck Mainframe Systems Programmer - TRA Enterprise Operations (Station 200) (005OP6.3.10) Information and Technology, IT Operations and Services -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Farley, Peter x23353 Sent: Monday, May 01, 2017 12:50 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [EXTERNAL] Re: Manual Naming for Local use [WAS: Issue with SK4T-4949-13 - IBM Online Library] BTW the "pdfinfo" command is available as a Windows binary available at the XPDF website: http://www.foolabs.com/xpdf/download.html The Windows package has only the command-line tools, of which "pdfinfo" is just one. A quite useful set of PDF tools, IMHO. HTH Peter -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John McKown Sent: Monday, May 01, 2017 1:12 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Manual Naming for Local use [WAS: Issue with SK4T-4949-13 - IBM Online Library] How I do it on Linux is to use the "pdfinfo" program. Example: [tsh009@it-johnmckown-linux Documents]$ pdfinfo dz9zr010.pdf Title: z/Architecture Principles of Operation Subject:z/Architecture Keywords: Author: IBM Corporation Creator:FrameMaker 10.0.2 Producer: Acrobat Distiller 10.1.13 (Windows) CreationDate: Thu Feb 19 17:32:41 2015 CST ModDate:Thu Feb 19 17:32:41 2015 CST Tagged: no UserProperties: no Suspects: no Form: AcroForm JavaScript: no Pages: 1732 Encrypted: no Page size: 612 x 792 pts (letter) Page rot: 0 File size: 15180376 bytes Optimized: yes PDF version:1.6 So for i in *.pdf;do ln -s "${i}" $(pdfinfo "${i}" | awk '$1=="Title:" {print $0;}' | sed -r 's/^Title: *//;s|/||g;s/ +/_/g;').pdf;done -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [EXTERNAL] Re: Manual Naming for Local use [WAS: Issue with SK4T-4949-13 - IBM Online Library....]
Tried it on Windows 10 bash shell and got a LOT of 'invalid argument' messages on the ln command - but not on all. Example: ln: failed to create symbolic link ‘zOS_V2R2.0_Communications_Server:_IP_Diagnosis_Guide.pdf’: Invalid argument ln: failed to create symbolic link ‘zOS_V2R2.0_Communications_Server:_SNA_Messages.pdf’: Invalid argument ln: failed to create symbolic link ‘zOS_V2R2.0_Communications_Server:_IP_Messages_Volume_1_(EZA).pdf’: Invalid argument ln: failed to create symbolic link ‘zOS_V2R2.0_Communications_Server:_IP_Messages_Volume_2_(EZB,_EZD).pdf’: Invalid argument -- Lionel B. Dyck Mainframe Systems Programmer - TRA Enterprise Operations (Station 200) (005OP6.3.10) Information and Technology, IT Operations and Services -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John McKown Sent: Monday, May 01, 2017 12:12 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [EXTERNAL] Re: Manual Naming for Local use [WAS: Issue with SK4T-4949-13 - IBM Online Library] On Mon, May 1, 2017 at 11:48 AM, Paul Gilmartin < 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > On Sun, 30 Apr 2017 10:32:50 -0400, Steve Thompson wrote: > > > >Example: iea2b6a0.pdf might become iea2b6a0_JCL_REF.pdf > > > >This was immediately slapped down as never gonna happen. > > > >Should this be put forth as a Share request/requirement? > > > 8.3 names should be left in the Dark Ages. The obstacle might be > updating all publications to use document titles in cross references > instead of 8.3 names. > > >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? > > > >And if one is a Windows user, can one easily do a link? > > > I got fancy. On MacOS X: > > I made no changes to the extracted .zip directory. > > Working in a new directory (in the same filesystem): > > o I created document titles as *hard* links to the 8.3 pdf files. > > o I created 8.3 names as symlinks to those hard links. > > Now, with Mac Preview, the document titles appear in window title bars > and File; Open Recent shows document titles. > > Adobe Reader shows the 83 names. > > In both cases, cross-references continue to work. > > Except, I used the HLASM General Info as a test because it has a nice > Bibliography. But some links there work; others don't. For example, > the link to the JCL User's Guide works; the link to the JCL Reference > doesn't. The filename appears to be wrong. > I'll submit an RCF. > > -- gil > How I do it on Linux is to use the "pdfinfo" program. Example: [tsh009@it-johnmckown-linux Documents]$ pdfinfo dz9zr010.pdf Title: z/Architecture Principles of Operation Subject:z/Architecture Keywords: Author: IBM Corporation Creator:FrameMaker 10.0.2 Producer: Acrobat Distiller 10.1.13 (Windows) CreationDate: Thu Feb 19 17:32:41 2015 CST ModDate:Thu Feb 19 17:32:41 2015 CST Tagged: no UserProperties: no Suspects: no Form: AcroForm JavaScript: no Pages: 1732 Encrypted: no Page size: 612 x 792 pts (letter) Page rot: 0 File size: 15180376 bytes Optimized: yes PDF version:1.6 So for i in *.pdf;do ln -s "${i}" $(pdfinfo "${i}" | awk '$1=="Title:" {print $0;}' | sed -r 's/^Title: *//;s|/||g;s/ +/_/g;').pdf;done -- Advertising is a valuable economic factor because it is the cheapest way of selling goods, particularly if the goods are worthless. -- Sinclair Lewis Maranatha! <>< John McKown -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: [EXTERNAL] Re: Manual Naming for Local use [WAS: Issue with SK4T-4949-13 - IBM Online Library....]
I found that under Windows 10 bash you can install the package with pdfinfo and it then the command seems to work - I haven't downloaded the zip file yet to try it out but sed, awk, etc. all seem to be in place under the bash shell. -- Lionel B. Dyck Mainframe Systems Programmer - TRA Enterprise Operations (Station 200) (005OP6.3.10) Information and Technology, IT Operations and Services -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Farley, Peter x23353 Sent: Monday, May 01, 2017 12:50 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [EXTERNAL] Re: Manual Naming for Local use [WAS: Issue with SK4T-4949-13 - IBM Online Library] BTW the "pdfinfo" command is available as a Windows binary available at the XPDF website: http://www.foolabs.com/xpdf/download.html The Windows package has only the command-line tools, of which "pdfinfo" is just one. A quite useful set of PDF tools, IMHO. HTH Peter -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John McKown Sent: Monday, May 01, 2017 1:12 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Manual Naming for Local use [WAS: Issue with SK4T-4949-13 - IBM Online Library] How I do it on Linux is to use the "pdfinfo" program. Example: [tsh009@it-johnmckown-linux Documents]$ pdfinfo dz9zr010.pdf Title: z/Architecture Principles of Operation Subject:z/Architecture Keywords: Author: IBM Corporation Creator:FrameMaker 10.0.2 Producer: Acrobat Distiller 10.1.13 (Windows) CreationDate: Thu Feb 19 17:32:41 2015 CST ModDate:Thu Feb 19 17:32:41 2015 CST Tagged: no UserProperties: no Suspects: no Form: AcroForm JavaScript: no Pages: 1732 Encrypted: no Page size: 612 x 792 pts (letter) Page rot: 0 File size: 15180376 bytes Optimized: yes PDF version:1.6 So for i in *.pdf;do ln -s "${i}" $(pdfinfo "${i}" | awk '$1=="Title:" {print $0;}' | sed -r 's/^Title: *//;s|/||g;s/ +/_/g;').pdf;done -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Manual Naming for Local use [WAS: Issue with SK4T-4949-13 - IBM Online Library....]
BTW the "pdfinfo" command is available as a Windows binary available at the XPDF website: http://www.foolabs.com/xpdf/download.html The Windows package has only the command-line tools, of which "pdfinfo" is just one. A quite useful set of PDF tools, IMHO. HTH Peter -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John McKown Sent: Monday, May 01, 2017 1:12 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Manual Naming for Local use [WAS: Issue with SK4T-4949-13 - IBM Online Library] How I do it on Linux is to use the "pdfinfo" program. Example: [tsh009@it-johnmckown-linux Documents]$ pdfinfo dz9zr010.pdf Title: z/Architecture Principles of Operation Subject:z/Architecture Keywords: Author: IBM Corporation Creator:FrameMaker 10.0.2 Producer: Acrobat Distiller 10.1.13 (Windows) CreationDate: Thu Feb 19 17:32:41 2015 CST ModDate:Thu Feb 19 17:32:41 2015 CST Tagged: no UserProperties: no Suspects: no Form: AcroForm JavaScript: no Pages: 1732 Encrypted: no Page size: 612 x 792 pts (letter) Page rot: 0 File size: 15180376 bytes Optimized: yes PDF version:1.6 So for i in *.pdf;do ln -s "${i}" $(pdfinfo "${i}" | awk '$1=="Title:" {print $0;}' | sed -r 's/^Title: *//;s|/||g;s/ +/_/g;').pdf;done -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Manual Naming for Local use [WAS: Issue with SK4T-4949-13 - IBM Online Library....]
On Mon, May 1, 2017 at 11:48 AM, Paul Gilmartin < 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > On Sun, 30 Apr 2017 10:32:50 -0400, Steve Thompson wrote: > > > >Example: iea2b6a0.pdf might become iea2b6a0_JCL_REF.pdf > > > >This was immediately slapped down as never gonna happen. > > > >Should this be put forth as a Share request/requirement? > > > 8.3 names should be left in the Dark Ages. The obstacle might > be updating all publications to use document titles in cross > references instead of 8.3 names. > > >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? > > > >And if one is a Windows user, can one easily do a link? > > > I got fancy. On MacOS X: > > I made no changes to the extracted .zip directory. > > Working in a new directory (in the same filesystem): > > o I created document titles as *hard* links to the 8.3 pdf files. > > o I created 8.3 names as symlinks to those hard links. > > Now, with Mac Preview, the document titles appear in window title > bars and File; Open Recent shows document titles. > > Adobe Reader shows the 83 names. > > In both cases, cross-references continue to work. > > Except, I used the HLASM General Info as a test because it has a > nice Bibliography. But some links there work; others don't. For > example, the link to the JCL User's Guide works; the link to the > JCL Reference doesn't. The filename appears to be wrong. > I'll submit an RCF. > > -- gil > How I do it on Linux is to use the "pdfinfo" program. Example: [tsh009@it-johnmckown-linux Documents]$ pdfinfo dz9zr010.pdf Title: z/Architecture Principles of Operation Subject:z/Architecture Keywords: Author: IBM Corporation Creator:FrameMaker 10.0.2 Producer: Acrobat Distiller 10.1.13 (Windows) CreationDate: Thu Feb 19 17:32:41 2015 CST ModDate:Thu Feb 19 17:32:41 2015 CST Tagged: no UserProperties: no Suspects: no Form: AcroForm JavaScript: no Pages: 1732 Encrypted: no Page size: 612 x 792 pts (letter) Page rot: 0 File size: 15180376 bytes Optimized: yes PDF version:1.6 So for i in *.pdf;do ln -s "${i}" $(pdfinfo "${i}" | awk '$1=="Title:" {print $0;}' | sed -r 's/^Title: *//;s|/||g;s/ +/_/g;').pdf;done -- Advertising is a valuable economic factor because it is the cheapest way of selling goods, particularly if the goods are worthless. -- Sinclair Lewis Maranatha! <>< John McKown -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Manual Naming for Local use [WAS: Issue with SK4T-4949-13 - IBM Online Library....]
On Sun, 30 Apr 2017 10:32:50 -0400, Steve Thompson wrote: > >Example: iea2b6a0.pdf might become iea2b6a0_JCL_REF.pdf > >This was immediately slapped down as never gonna happen. > >Should this be put forth as a Share request/requirement? > 8.3 names should be left in the Dark Ages. The obstacle might be updating all publications to use document titles in cross references instead of 8.3 names. >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? > >And if one is a Windows user, can one easily do a link? > I got fancy. On MacOS X: I made no changes to the extracted .zip directory. Working in a new directory (in the same filesystem): o I created document titles as *hard* links to the 8.3 pdf files. o I created 8.3 names as symlinks to those hard links. Now, with Mac Preview, the document titles appear in window title bars and File; Open Recent shows document titles. Adobe Reader shows the 83 names. In both cases, cross-references continue to work. Except, I used the HLASM General Info as a test because it has a nice Bibliography. But some links there work; others don't. For example, the link to the JCL User's Guide works; the link to the JCL Reference doesn't. The filename appears to be wrong. I'll submit an RCF. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Manual Naming for Local use [WAS: Issue with SK4T-4949-13 - IBM Online Library....]
On Sun, 30 Apr 2017 10:32:50 -0400, Steve Thompson wrote: > >Example: iea2b6a0.pdf might become iea2b6a0_JCL_REF.pdf > >This was immediately slapped down as never gonna happen. > >But, what if IBM were to do this naming? > >Should this be put forth as a Share request/requirement? > Why is this 8.3 crap still a thing? What century is this? (But the obscure names might be deeply embedded in cross-document references.) -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Manual Naming for Local use [WAS: Issue with SK4T-4949-13 - IBM Online Library....]
On Sun, 30 Apr 2017 10:52:27 -0700, Tom Brennan wrote: >That happens to me too, because I rename the PDF files at download time >(and even organize them in various directories). So none of the external >links work. > >Maybe next time I'll try creating Windows shortcuts instead of renaming. > For example, if I download has2x311.pdf and create a shortcut to it >named "JES2 Messages", I can find it easily by using the shortcut, and >then links in has2v511.pdf "JES2 Init and Tuning Guide" can also find it >by the original filename. No changes needed by IBM - just shortcuts. > When I do this with symlinks (don't know shortcuts), most things work, but Adobe Reader "Open Recent File" shows the obscure name, not the link name. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Manual Naming for Local use [WAS: Issue with SK4T-4949-13 - IBM Online Library....]
On Sun, 30 Apr 2017 12:47:38 -0600, Mark Post wrote: >>> >> 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. > >These two things, taken together, is what "wget -k" does. If you do a "wget >-k -p" on a web page, you'll get all the elements of the page (excluding those >defined in javascript), with the HTML modified to point to the local copy. > Isn't that what the HTML (IIRC) markup does. (At least for relative links.) Again, why not just download and extract the .zip. At least for z/OS 2.2. For other libraries, it may be harder, >For myself, I download all the Linux and z/VM presentations from the various >SHARE conferences I attend. I wrote a shell script to download all the PDF >files, and use the various HTML files to create symbolic links to them using >the title of the presentation. It works well enough for my needs. > >On Linux systems the poppler-tools package contains a "pdfinfo" command that >can print things like Title and Author from PDF files that contain them. This >could aid in creating symbolic links via scripting as well. > Here's my script: 615 $ cat ~/bin/foodex; ls -al | head -11 #! /bin/sh -x sed -n ' s/[\/]/_/g s/[^<]*\([^<]*\).*href="\(.[^"]*\)".*/ln -s "..\/SC27-8430-05\/\2" "\1"/p ' ../SC27-8430-05/index.html total 2600 ... and sample output. drwxr-xr-x 2 paulgilm wheel 8 Apr 30 13:25 . drwxr-xr-x 4 paulgilm wheel238 Apr 30 13:10 .. lrwxr-xr-x 1 paulgilm wheel 28 Apr 30 13:25 AFP Conversion and Indexing Facility User's Guide -> ../SC27-8430-05/aps4ac40.pdf lrwxr-xr-x 1 paulgilm wheel 28 Apr 30 13:25 DWARF_ELF Extensions Library Reference -> ../SC27-8430-05/cbb1d210.pdf lrwxr-xr-x 1 paulgilm wheel 28 Apr 30 13:25 Device Support Facilities (ICKDSF) User's Guide and Reference -> ../SC27-8430-05/ick4020o.pdf lrwxr-xr-x 1 paulgilm wheel 28 Apr 30 13:25 EREP Reference -> ../SC27-8430-05/ifc5r107.pdf lrwxr-xr-x 1 paulgilm wheel 28 Apr 30 13:25 EREP User's Guide -> ../SC27-8430-05/ifc5g104.pdf lrwxr-xr-x 1 paulgilm wheel 28 Apr 30 13:25 HLASM General Information -> ../SC27-8430-05/asmg1022.pdf lrwxr-xr-x 1 paulgilm wheel 28 Apr 30 13:25 HLASM Installation and Customization Guide -> ../SC27-8430-05/asmi1022.pdf lrwxr-xr-x 1 paulgilm wheel 28 Apr 30 13:25 HLASM Language Reference -> ../SC27-8430-05/asmr1022.pdf ... most of the cross-document links work; others don't; I don't know why; others are http:// links. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Manual Naming for Local use [WAS: Issue with SK4T-4949-13 - IBM Online Library....]
>>> On 4/30/2017 at 12:40 PM, Paul Gilmartin <000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > 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. These two things, taken together, is what "wget -k" does. If you do a "wget -k -p" on a web page, you'll get all the elements of the page (excluding those defined in javascript), with the HTML modified to point to the local copy. For myself, I download all the Linux and z/VM presentations from the various SHARE conferences I attend. I wrote a shell script to download all the PDF files, and use the various HTML files to create symbolic links to them using the title of the presentation. It works well enough for my needs. On Linux systems the poppler-tools package contains a "pdfinfo" command that can print things like Title and Author from PDF files that contain them. This could aid in creating symbolic links via scripting as well. Mark Post -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Manual Naming for Local use [WAS: Issue with SK4T-4949-13 - IBM Online Library....]
That happens to me too, because I rename the PDF files at download time (and even organize them in various directories). So none of the external links work. Maybe next time I'll try creating Windows shortcuts instead of renaming. For example, if I download has2x311.pdf and create a shortcut to it named "JES2 Messages", I can find it easily by using the shortcut, and then links in has2v511.pdf "JES2 Init and Tuning Guide" can also find it by the original filename. No changes needed by IBM - just shortcuts. For that to work, I think I would have to pile all the PDF's into the same directory, but I can still split my shortcuts into separate directories (i.e. JES2, MVS, ISPF, etc.) to make it easy on me. Nims,Alva John (Al) wrote: For my $0.02, yes I too would like to see the file names match the manual title, BUT there is a little flaw in doing this. Sometimes within a manual there will be a link referencing another manual and that link should you click on it, will be using the file name that IBM assigns. I do not run across it often and it does now fall within the "it would be nice if ," but it is easy enough for me to go and find the manual and open it esternally. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Manual Naming for Local use [WAS: Issue with SK4T-4949-13 - IBM Online Library....]
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? > >And if one is a Windows user, can one easily do a link? > (more) You might use way long names incorporating Order number, OS release, Shelf name, ..., and rely on file manager's filtering by name. On Linux, I see: -bash 3+ man zip ZIP(1) ... --symlinks For UNIX and VMS (V8.3 and later), store symbolic links as such in the zip archive, instead of compressing and storing the file referred to by the link. This can avoid multiple copies of files being included in the archive as zip recurses the directory trees and accesses files directly and by links. ... I have no idea what happens if a filesystem so stored is unzipped on a system not supporting symlinks. Will it use Windows' "mklink"? Shortcuts? -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Manual Naming for Local use [WAS: Issue with SK4T-4949-13 - IBM Online Library....]
For my $0.02, yes I too would like to see the file names match the manual title, BUT there is a little flaw in doing this. Sometimes within a manual there will be a link referencing another manual and that link should you click on it, will be using the file name that IBM assigns. I do not run across it often and it does now fall within the "it would be nice if ," but it is easy enough for me to go and find the manual and open it esternally. Al Nims Systems Admin/Programmer 3 UFIT University of Florida (352) 273-1298 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Paul Gilmartin Sent: Sunday, April 30, 2017 12:41 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Manual Naming for Local use [WAS: Issue with SK4T-4949-13 - IBM Online Library] 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 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Manual Naming for Local use [WAS: Issue with SK4T-4949-13 - IBM Online Library....]
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
Manual Naming for Local use [WAS: Issue with SK4T-4949-13 - IBM Online Library....]
More than a year ago (it may have been 2012, I just can't remember), I put forth an idea that IBM do a search for its manuals based on their ID for the manuals, while the user could name that manual from that point. Example: iea2b6a0.pdf might become iea2b6a0_JCL_REF.pdf This was immediately slapped down as never gonna happen. But, what if IBM were to do this naming? Should this be put forth as a Share request/requirement? 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? And if one is a Windows user, can one easily do a link? 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. Regards, Steve Thompson On 04/29/2017 08:11 PM, Brian Westerman wrote: I rename a few of the manuals (the ones I use all the time), but I too wish the file names of the manuals were the full manual name. I would hate to think about trying to rename hundreds of manuals each time, I would go nuts, but I do copy about 20 of them that I really care about. Using the index is great (I rename that too), but it still would be nice to have better names on the individual files. Brian -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN