Re: SHOW still available ?
SPOOLAID cannot be compared to SHOW/PEEK/VM:SPOOL as it displays raw spool data. Note too that PEEK, SHOW and Spoolaid only display spool files sitting in your own reader. 2007/7/9, Les Geer (607-429-3580) [EMAIL PROTECTED]: I've been searching for a tool to read the vm spool and ran across some references to a SHOW tool but I've not been able to find a download site for it. If you have RSCS, you can use the spoolaid package to view spool files. This package can be found on the install ID's 406 minidisk. Best Regards, Les Geer IBM z/VM and Linux Development -- Kris Buelens, IBM Belgium, VM customer support
Re: SHOW still available ?
Les - thanks for the suggestion. I don't have RSCS (can't justify it for our site) Lionel B. Dyck, Consultant/Specialist Enterprise Platform Services, Mainframe Engineering KP-IT Enterprise Engineering, Client and Platform Engineering Services (CAPES) 925-926-5332 (8-473-5332) | E-Mail: [EMAIL PROTECTED] AIM: lbdyck | Yahoo IM: lbdyck Kaiser Service Credo: Our cause is health. Our passion is service. We?re here to make lives better.? ?Never attribute to malice what can be caused by miscommunication.? NOTICE TO RECIPIENT: If you are not the intended recipient of this e-mail, you are prohibited from sharing, copying, or otherwise using or disclosing its contents. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and permanently delete this e-mail and any attachments without reading, forwarding or saving them. Thank you. Les Geer (607-429-3580) [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 07/08/2007 08:13 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: SHOW still available ? I've been searching for a tool to read the vm spool and ran across some references to a SHOW tool but I've not been able to find a download site for it. If you have RSCS, you can use the spoolaid package to view spool files. This package can be found on the install ID's 406 minidisk. Best Regards, Les Geer IBM z/VM and Linux Development
Re: SHOW still available ?
With CA's VM:SPOOL you can look at other user's spool files, and even if they are still open. 2007/7/9, Lionel B. Dyck [EMAIL PROTECTED]: Thanks - Found it and downloaded. Is there any 'trick' to using it to view a file in the spool, specifically a prt file for another account? Thanks -- *Lionel B. Dyck, Consultant/Specialist * Enterprise Platform Services, Mainframe Engineering KP-IT Enterprise Engineering, Client and Platform Engineering Services (CAPES) 925-926-5332 (8-473-5332) | E-Mail: [EMAIL PROTECTED][EMAIL PROTECTED] AIM: lbdyck *|* Yahoo IM: lbdyck * * -- Kris Buelens, IBM Belgium, VM customer support
Re: SHOW still available ?
If your virtual machine has the needed set of CP privileges, you can TRANSFER the prt file from the owning user's prt queue to your RDR queue. SHOW can then browse it Try reading the onlne help for the TRANSFER command. Lionel B. Dyck wrote: Thanks - Found it and downloaded. Is there any 'trick' to using it to view a file in the spool, specifically a prt file for another account? Thanks Lionel B. Dyck, Consultant/Specialist Enterprise Platform Services, Mainframe Engineering KP-IT Enterprise Engineering, Client and Platform Engineering Services (CAPES) 925-926-5332 (8-473-5332) | E-Mail: [EMAIL PROTECTED] AIM: lbdyck | Yahoo IM: lbdyck Kaiser Service Credo: Our cause is health. Our passion is service. We?re here to make lives better.? ?Never attribute to malice what can be caused by miscommunication.? NOTICE TO RECIPIENT: If you are not the intended recipient of this e-mail, you are prohibited from sharing, copying, or otherwise using or disclosing its contents. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and permanently delete this e-mail and any attachments without reading, forwarding or saving them. Thank you. Dave Jones [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 07/07/2007 10:36 AM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: SHOW still available ? Hi, Lionel. I believe you can download the latest version of SHOW (and, yes, you really do need to have it handy:-) from Fran Hensler's web site at: http://zvm.sru.edu/~DOWNLOAD/ Good luck, and welcome to the z/VM community as well. DJ Lionel B. Dyck wrote: I've been searching for a tool to read the vm spool and ran across some references to a SHOW tool but I've not been able to find a download site for it. Does it still exist? If not is there any alternative to viewing spool files? thanks Lionel B. Dyck, Consultant/Specialist Enterprise Platform Services, Mainframe Engineering KP-IT Enterprise Engineering, Client and Platform Engineering Services (CAPES) 925-926-5332 (8-473-5332) | E-Mail: [EMAIL PROTECTED] AIM: lbdyck | Yahoo IM: lbdyck Kaiser Service Credo: Our cause is health. Our passion is service. We?re here to make lives better.? ?Never attribute to malice what can be caused by miscommunication.? NOTICE TO RECIPIENT: If you are not the intended recipient of this e-mail, you are prohibited from sharing, copying, or otherwise using or disclosing its contents. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and permanently delete this e-mail and any attachments without reading, forwarding or saving them. Thank you. -- DJ V/Soft
Re: SHOW still available ?
DAVE's words about TRANSFER brings some memories back: You also might want to have a look at my URLIST package: it shows the RDR/PUN/PRT queue of other users in an RDRLIST-like way. It provides a PEEK command, but that PEEK will involve a TRANSFER of the file to your RDR-queue, PEEK, and TRANSFER back. Drawback: this TRANSFER process will change the spool file number (and if you'd LOGOFF before we can transfer back, the file remains in your reader). 2007/7/9, Dave Jones [EMAIL PROTECTED]: If your virtual machine has the needed set of CP privileges, you can TRANSFER the prt file from the owning user's prt queue to your RDR queue. SHOW can then browse it Try reading the onlne help for the TRANSFER command. -- DJ V/Soft -- Kris Buelens, IBM Belgium, VM customer support
Obituary - Donald Michie
From today's AP wire: --- cut here --- Donald Michie and Anne McLaren LONDON (AP) -- British artificial intelligence expert, Donald Michie, and an ex-wife, leading geneticist Dame Anne McLaren, have died in a car crash. Michie, 84, and McLaren, 80, were killed Saturday when their car veered off a highway while they were traveling from Cambridge to their home in London, said their son, Jonathan Michie. Michie was a pioneering artificial intelligence researcher who worked as part of the British code-breaking group at Bletchley Park during World War II. He contributed to the effort to solve Tunny, a German teleprinter cipher. He was appointed director of the University of Edinburgh's Department of Machine Intelligence and Perception when it was established in 1966 and was founder and editor-in-chief of the Machine Intelligence publication series. His former wife, McLaren, with whom he remained close friends after their divorce in 1959, was a leading geneticist who became the first female officer of the Royal Society, holding the post of foreign secretary from 1991-1996. She was a member of an independent committee appointed by the government to investigate new reproductive technologies after the birth of the world's first test-tube baby here in 1978 and make recommendations on the freezing and storage of human embryos and their use in research. Queen Elizabeth II named her a dame commander of the British Empire in 1993 and she was a fellow of King's College and Christ College at the University of Cambridge. --- cut here --- -dan.
What VM oldest level can you bring Z/VM 5.3 2nd level?
Actually: Can you bring it up under VM 2.2 ( I was thinking no, but I don't find anything on the VM web page) __ This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message. To reply to our email administrator directly, send an email to [EMAIL PROTECTED]
Philosophy on Tool Installations
What is the best practice for installing tools into the z/VM space? 1. Do you create a mini-disk for each tool and have everyone who needs it link to that disk for the time needed to use the tool? 2. Do you create a common mini-disk that is accessed by every user? (in z/OS I would put the tools into their own libraries and then put those libraries into the linklist if everyone needed access or provide information on how to steplib for those infrequent uses). Thanks (and please forgive the mention of z/OS) Lionel B. Dyck, Consultant/Specialist Enterprise Platform Services, Mainframe Engineering KP-IT Enterprise Engineering, Client and Platform Engineering Services (CAPES) 925-926-5332 (8-473-5332) | E-Mail: [EMAIL PROTECTED] AIM: lbdyck | Yahoo IM: lbdyck Kaiser Service Credo: Our cause is health. Our passion is service. We?re here to make lives better.? ?Never attribute to malice what can be caused by miscommunication.? NOTICE TO RECIPIENT: If you are not the intended recipient of this e-mail, you are prohibited from sharing, copying, or otherwise using or disclosing its contents. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and permanently delete this e-mail and any attachments without reading, forwarding or saving them. Thank you.
Re: What VM oldest level can you bring Z/VM 5.3 2nd level?
z/VM 5.x must run in a 64-bit machine. As I recall the first VM that supported 64-bit virtual machines was 3.1. So z/VM 5.3 running as a guest would need to be on a 3.1 or higher VM. [EMAIL PROTECTED] wrote: Actually: Can you bring it up under VM 2.2 ( I was thinking no, but I don't find anything on the VM web page) -- Stephen Frazier Information Technology Unit Oklahoma Department of Corrections 3400 Martin Luther King Oklahoma City, Ok, 73111-4298 Tel.: (405) 425-2549 Fax: (405) 425-2554 Pager: (405) 690-1828 email: stevef%doc.state.ok.us
Re: Philosophy on Tool Installations
The answer is yes. A tool that is only needed by a few would be placed on its own mini-disk and linked to by those who need it. A tool that is used by almost everyone is placed on the Y disk so everyone has access to it all the time. [EMAIL PROTECTED] wrote: What is the best practice for installing tools into the z/VM space? 1. Do you create a mini-disk for each tool and have everyone who needs it link to that disk for the time needed to use the tool? 2. Do you create a common mini-disk that is accessed by every user? (in z/OS I would put the tools into their own libraries and then put those libraries into the linklist if everyone needed access or provide information on how to steplib for those infrequent uses). Thanks (and please forgive the mention of z/OS) -- Stephen Frazier Information Technology Unit Oklahoma Department of Corrections 3400 Martin Luther King Oklahoma City, Ok, 73111-4298 Tel.: (405) 425-2549 Fax: (405) 425-2554 Pager: (405) 690-1828 email: stevef%doc.state.ok.us
Re: Philosophy on Tool Installations
I try to use a separate minidisk/sfs-directory for the installation and maintenance of each tool. But for production, I try to have two minidisks , one for general users and one for sysprogs. The Y-disk is my favorite spo t for the general user tools. On my IFL VM system, I am trying to use R for the sysprog disk (MAINT 19F). BTW, don't worry about using that name (z/OS) or even that other name (MV S). A lot of us have been providing virtual machines for those systems to run in for a long time. :) /Tom Kern /301-903-2211 On Mon, 9 Jul 2007 13:30:19 -0700, Lionel B. Dyck [EMAIL PROTECTED] wrote: What is the best practice for installing tools into the z/VM space? 1. Do you create a mini-disk for each tool and have everyone who needs i t link to that disk for the time needed to use the tool? 2. Do you create a common mini-disk that is accessed by every user? (in z/OS I would put the tools into their own libraries and then put tho se libraries into the linklist if everyone needed access or provide information on how to steplib for those infrequent uses). Thanks (and please forgive the mention of z/OS) Lionel B. Dyck, Consultant/Specialist
Re: SHOW still available ?
Kris - your tool looks very nice - thank you for sharing it. Since it will not view open files I am going to have to look for a product (VM:Spool it would appear). Thanks Lionel B. Dyck, Consultant/Specialist Enterprise Platform Services, Mainframe Engineering KP-IT Enterprise Engineering, Client and Platform Engineering Services (CAPES) 925-926-5332 (8-473-5332) | E-Mail: [EMAIL PROTECTED] AIM: lbdyck | Yahoo IM: lbdyck Kaiser Service Credo: Our cause is health. Our passion is service. We?re here to make lives better.? ?Never attribute to malice what can be caused by miscommunication.? NOTICE TO RECIPIENT: If you are not the intended recipient of this e-mail, you are prohibited from sharing, copying, or otherwise using or disclosing its contents. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and permanently delete this e-mail and any attachments without reading, forwarding or saving them. Thank you. Kris Buelens [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 07/09/2007 08:09 AM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: SHOW still available ? DAVE's words about TRANSFER brings some memories back: You also might want to have a look at my URLIST package: it shows the RDR/PUN/PRT queue of other users in an RDRLIST-like way. It provides a PEEK command, but that PEEK will involve a TRANSFER of the file to your RDR-queue, PEEK, and TRANSFER back. Drawback: this TRANSFER process will change the spool file number (and if you'd LOGOFF before we can transfer back, the file remains in your reader). 2007/7/9, Dave Jones [EMAIL PROTECTED]: If your virtual machine has the needed set of CP privileges, you can TRANSFER the prt file from the owning user's prt queue to your RDR queue. SHOW can then browse it Try reading the onlne help for the TRANSFER command. -- DJ V/Soft -- Kris Buelens, IBM Belgium, VM customer support
Re: What VM oldest level can you bring Z/VM 5.3 2nd level?
And, as I recall, there were problems going from VM/ESA 2.2 to some later z/VM releases, like 4.2; we had to go to 2.4 before we could get 4.2 to come up second-level. I don't know if 3.1 would have the same problems coming from 2.2. (Anybody got Bingo! yet on their releases Bingo card?) Nick Stephen Frazier wrote: z/VM 5.x must run in a 64-bit machine. As I recall the first VM that supported 64-bit virtual machines was 3.1. So z/VM 5.3 running as a guest would need to be on a 3.1 or higher VM. [EMAIL PROTECTED] wrote: Actually: Can you bring it up under VM 2.2 ( I was thinking no, but I don't find anything on the VM web page)
Re: SHOW still available ?
You might want to checkout SPEDIT .. very good for the price. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] Behalf Of Lionel B. Dyck Sent: Monday, July 09, 2007 3:40 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SHOW still available ? Kris - your tool looks very nice - thank you for sharing it. Since it will not view open files I am going to have to look for a product (VM:Spool it would appear). Thanks _ Lionel B. Dyck, Consultant/Specialist Enterprise Platform Services, Mainframe Engineering KP-IT Enterprise Engineering, Client and Platform Engineering Services (CAPES) 925-926-5332 (8-473-5332) | E-Mail: mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] AIM: lbdyck | Yahoo IM: lbdyck Kaiser Service Credo: Our cause is health. Our passion is service. We're here to make lives better. Never attribute to malice what can be caused by miscommunication. NOTICE TO RECIPIENT: If you are not the intended recipient of this e-mail, you are prohibited from sharing, copying, or otherwise using or disclosing its contents. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and permanently delete this e-mail and any attachments without reading, forwarding or saving them. Thank you. Kris Buelens [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 07/09/2007 08:09 AM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: SHOW still available ? DAVE's words about TRANSFER brings some memories back: You also might want to have a look at my URLIST package: it shows the RDR/PUN/PRT queue of other users in an RDRLIST-like way. It provides a PEEK command, but that PEEK will involve a TRANSFER of the file to your RDR-queue, PEEK, and TRANSFER back. Drawback: this TRANSFER process will change the spool file number (and if you'd LOGOFF before we can transfer back, the file remains in your reader). 2007/7/9, Dave Jones mailto:[EMAIL PROTECTED] [EMAIL PROTECTED]: If your virtual machine has the needed set of CP privileges, you can TRANSFER the prt file from the owning user's prt queue to your RDR queue. SHOW can then browse it Try reading the onlne help for the TRANSFER command. -- DJ V/Soft -- Kris Buelens, IBM Belgium, VM customer support _ ella for Spam Control has removed 12382 VSE-List messages and set aside 11082 VM-List for me You can use it too - and it's FREE! www.ellaforspam.com http://www.ellaforspam.com
Re: Philosophy on Tool Installations
We have three separate tools disks. They are 1) local tools for general use accessed as filemode X, 2) a systems programming tools disk for systems programming users and various service machines accessed as filemode F, and 3) a developer maintained tools disk for our development folks and it is accessed before the local tools disk but after the S-disk as filemode T. We have some program product disks which are separated out by IBM and non-IBM products and they are accessed between S and Z. These are all fixed at logon time. Some tools/products that require a disk load of stuff get accessed by an invocation EXEC on the appropriate tools disk (normally determined by who supports the EXEC). - Judson West Teradata, a division of NCR Corporation _ From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Lionel B. Dyck Sent: Monday, July 09, 2007 1:30 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Philosophy on Tool Installations What is the best practice for installing tools into the z/VM space? 1. Do you create a mini-disk for each tool and have everyone who needs it link to that disk for the time needed to use the tool? 2. Do you create a common mini-disk that is accessed by every user? (in z/OS I would put the tools into their own libraries and then put those libraries into the linklist if everyone needed access or provide information on how to steplib for those infrequent uses). Thanks (and please forgive the mention of z/OS) _ Lionel B. Dyck, Consultant/Specialist Enterprise Platform Services, Mainframe Engineering KP-IT Enterprise Engineering, Client and Platform Engineering Services (CAPES) 925-926-5332 (8-473-5332) | E-Mail: mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] AIM: lbdyck | Yahoo IM: lbdyck Kaiser Service Credo: Our cause is health. Our passion is service. We're here to make lives better. Never attribute to malice what can be caused by miscommunication. NOTICE TO RECIPIENT: If you are not the intended recipient of this e-mail, you are prohibited from sharing, copying, or otherwise using or disclosing its contents. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and permanently delete this e-mail and any attachments without reading, forwarding or saving them. Thank you.
Re: Philosophy on Tool Installations
On Jul 9, 2007, at 3:39 PM, Stephen Frazier wrote: The answer is yes. A tool that is only needed by a few would be placed on its own mini-disk and linked to by those who need it. A tool that is used by almost everyone is placed on the Y disk so everyone has access to it all the time. [EMAIL PROTECTED] wrote: What is the best practice for installing tools into the z/VM space? 1. Do you create a mini-disk for each tool and have everyone who needs it link to that disk for the time needed to use the tool? 2. Do you create a common mini-disk that is accessed by every user? (in z/OS I would put the tools into their own libraries and then put those libraries into the linklist if everyone needed access or provide information on how to steplib for those infrequent uses). Thanks (and please forgive the mention of z/OS) I recommend using SFS rather than a minidisk, myself. Wastes less space, and I find that directories are easier to manage than keeping track of a bunch of different minidisks with no hierarchical organization. Adam
Re: Philosophy on Tool Installations
Our philosophy has always been to leave the 19E/Y-disk for IBM. 3rd Party and homegrown public tools were put on our P-disk (public), 19A at MSU. A hook into SYSPROF accessed this for all users. (Sysprog tools were on a separate disk, as are Ops-only tools) Accessing our public disk at P meant that it was searched prior to the S or Y, so that we could put cover Execs and the like on it. Some tools (certain compilers and database software --- things with lots of individual files) were kept on their own disks, with front-end wrappers placed put on our P-disk to Link/Access/Execute those tools. These wrappers were 1-liner execs which called a generic table-lookup/link/access tool, also on our P-disk. Thus when changes we needed to the wrappers they could be done in a single executable. Stephen Frazier wrote: The answer is yes. A tool that is only needed by a few would be placed on its own mini-disk and linked to by those who need it. A tool that is used by almost everyone is placed on the Y disk so everyone has access to it all the time. [EMAIL PROTECTED] wrote: What is the best practice for installing tools into the z/VM space? 1. Do you create a mini-disk for each tool and have everyone who needs it link to that disk for the time needed to use the tool? 2. Do you create a common mini-disk that is accessed by every user? (in z/OS I would put the tools into their own libraries and then put those libraries into the linklist if everyone needed access or provide information on how to steplib for those infrequent uses). Thanks (and please forgive the mention of z/OS)
Re: Philosophy on Tool Installations
As Adam had already mentioned, using the SFS to store either site specific or generic VM tools and utilities is a good idea. It has the following advantages over using minidisks: 1) easier to maintain multiple versions of a tool; different versions in separate subdirectories 2) easier to keep track of what's what. 3) much better control of file access permissions; both by directory and by individual files in a directory 4) less wasted space Also, look into using the IBM provided VMLINK utility for users to access the tool repositories they need (either those stored on minidisks or in SFS directories...). It's a very handy way of making tools and products available; and it can handle dependencies between tools and products as well. Check it out George Haddad wrote: Our philosophy has always been to leave the 19E/Y-disk for IBM. 3rd Party and homegrown public tools were put on our P-disk (public), 19A at MSU. A hook into SYSPROF accessed this for all users. (Sysprog tools were on a separate disk, as are Ops-only tools) Accessing our public disk at P meant that it was searched prior to the S or Y, so that we could put cover Execs and the like on it. Some tools (certain compilers and database software --- things with lots of individual files) were kept on their own disks, with front-end wrappers placed put on our P-disk to Link/Access/Execute those tools. These wrappers were 1-liner execs which called a generic table-lookup/link/access tool, also on our P-disk. Thus when changes we needed to the wrappers they could be done in a single executable. Stephen Frazier wrote: The answer is yes. A tool that is only needed by a few would be placed on its own mini-disk and linked to by those who need it. A tool that is used by almost everyone is placed on the Y disk so everyone has access to it all the time. [EMAIL PROTECTED] wrote: What is the best practice for installing tools into the z/VM space? 1. Do you create a mini-disk for each tool and have everyone who needs it link to that disk for the time needed to use the tool? 2. Do you create a common mini-disk that is accessed by every user? (in z/OS I would put the tools into their own libraries and then put those libraries into the linklist if everyone needed access or provide information on how to steplib for those infrequent uses). Thanks (and please forgive the mention of z/OS) -- DJ V/Soft
Re: What VM oldest level can you bring Z/VM 5.3 2nd level?
On Monday, 07/09/2007 at 12:49 MST, [EMAIL PROTECTED] wrote: Actually: Can you bring it up under VM 2.2 No. z/VM V5 requires z/Architecture, but VM/ESA does not support z/Architecture guests. Alan Altmark z/VM Development IBM Endicott
Re: SHOW still available ?
Does SPEDIT allow you to view an active/open spool file? I'm assuming VM:Spool does as I seem to recall being told that (but can't recall for sure) Thanks Lionel B. Dyck, Consultant/Specialist Enterprise Platform Services, Mainframe Engineering KP-IT Enterprise Engineering, Client and Platform Engineering Services (CAPES) 925-926-5332 (8-473-5332) | E-Mail: [EMAIL PROTECTED] AIM: lbdyck | Yahoo IM: lbdyck Kaiser Service Credo: Our cause is health. Our passion is service. We?re here to make lives better.? ?Never attribute to malice what can be caused by miscommunication.? NOTICE TO RECIPIENT: If you are not the intended recipient of this e-mail, you are prohibited from sharing, copying, or otherwise using or disclosing its contents. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and permanently delete this e-mail and any attachments without reading, forwarding or saving them. Thank you. Huegel, Thomas [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 07/09/2007 01:45 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: SHOW still available ? You might want to checkout SPEDIT .. very good for the price. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] Behalf Of Lionel B. Dyck Sent: Monday, July 09, 2007 3:40 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SHOW still available ? Kris - your tool looks very nice - thank you for sharing it. Since it will not view open files I am going to have to look for a product (VM:Spool it would appear). Thanks Lionel B. Dyck, Consultant/Specialist Enterprise Platform Services, Mainframe Engineering KP-IT Enterprise Engineering, Client and Platform Engineering Services (CAPES) 925-926-5332 (8-473-5332) | E-Mail: [EMAIL PROTECTED] AIM: lbdyck | Yahoo IM: lbdyck Kaiser Service Credo: Our cause is health. Our passion is service. We're here to make lives better. Never attribute to malice what can be caused by miscommunication. NOTICE TO RECIPIENT: If you are not the intended recipient of this e-mail, you are prohibited from sharing, copying, or otherwise using or disclosing its contents. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and permanently delete this e-mail and any attachments without reading, forwarding or saving them. Thank you. Kris Buelens [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 07/09/2007 08:09 AM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: SHOW still available ? DAVE's words about TRANSFER brings some memories back: You also might want to have a look at my URLIST package: it shows the RDR/PUN/PRT queue of other users in an RDRLIST-like way. It provides a PEEK command, but that PEEK will involve a TRANSFER of the file to your RDR-queue, PEEK, and TRANSFER back. Drawback: this TRANSFER process will change the spool file number (and if you'd LOGOFF before we can transfer back, the file remains in your reader). 2007/7/9, Dave Jones [EMAIL PROTECTED]: If your virtual machine has the needed set of CP privileges, you can TRANSFER the prt file from the owning user's prt queue to your RDR queue. SHOW can then browse it Try reading the onlne help for the TRANSFER command. -- DJ V/Soft -- Kris Buelens, IBM Belgium, VM customer support ella for Spam Control has removed 12382 VSE-List messages and set aside 11082 VM-List for me You can use it too - and it's FREE! www.ellaforspam.com
Re: SHOW still available ?
Yes it does. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] Behalf Of Lionel B. Dyck Sent: Monday, July 09, 2007 5:13 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SHOW still available ? Does SPEDIT allow you to view an active/open spool file? I'm assuming VM:Spool does as I seem to recall being told that (but can't recall for sure) Thanks _ Lionel B. Dyck, Consultant/Specialist Enterprise Platform Services, Mainframe Engineering KP-IT Enterprise Engineering, Client and Platform Engineering Services (CAPES) 925-926-5332 (8-473-5332) | E-Mail: mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] AIM: lbdyck | Yahoo IM: lbdyck Kaiser Service Credo: Our cause is health. Our passion is service. We're here to make lives better. Never attribute to malice what can be caused by miscommunication. NOTICE TO RECIPIENT: If you are not the intended recipient of this e-mail, you are prohibited from sharing, copying, or otherwise using or disclosing its contents. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and permanently delete this e-mail and any attachments without reading, forwarding or saving them. Thank you. Huegel, Thomas [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 07/09/2007 01:45 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: SHOW still available ? You might want to checkout SPEDIT .. very good for the price. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] Behalf Of Lionel B. Dyck Sent: Monday, July 09, 2007 3:40 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SHOW still available ? Kris - your tool looks very nice - thank you for sharing it. Since it will not view open files I am going to have to look for a product (VM:Spool it would appear). Thanks _ Lionel B. Dyck, Consultant/Specialist Enterprise Platform Services, Mainframe Engineering KP-IT Enterprise Engineering, Client and Platform Engineering Services (CAPES) 925-926-5332 (8-473-5332) | E-Mail: mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] AIM: lbdyck | Yahoo IM: lbdyck Kaiser Service Credo: Our cause is health. Our passion is service. We're here to make lives better. Never attribute to malice what can be caused by miscommunication. NOTICE TO RECIPIENT: If you are not the intended recipient of this e-mail, you are prohibited from sharing, copying, or otherwise using or disclosing its contents. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and permanently delete this e-mail and any attachments without reading, forwarding or saving them. Thank you. Kris Buelens [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 07/09/2007 08:09 AM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: SHOW still available ? DAVE's words about TRANSFER brings some memories back: You also might want to have a look at my URLIST package: it shows the RDR/PUN/PRT queue of other users in an RDRLIST-like way. It provides a PEEK command, but that PEEK will involve a TRANSFER of the file to your RDR-queue, PEEK, and TRANSFER back. Drawback: this TRANSFER process will change the spool file number (and if you'd LOGOFF before we can transfer back, the file remains in your reader). 2007/7/9, Dave Jones mailto:[EMAIL PROTECTED] [EMAIL PROTECTED]: If your virtual machine has the needed set of CP privileges, you can TRANSFER the prt file from the owning user's prt queue to your RDR queue. SHOW can then browse it Try reading the onlne help for the TRANSFER command. -- DJ V/Soft -- Kris Buelens, IBM Belgium, VM customer support _ ella for Spam Control has removed 12382 VSE-List messages and set aside 11082 VM-List for me You can use it too - and it's FREE!http://www.ellaforspam.com/ www.ellaforspam.com _ ella for Spam Control has removed 12383 VSE-List messages and set aside 11089 VM-List for me You can use it too - and it's FREE! www.ellaforspam.com http://www.ellaforspam.com
Re: Philosophy on Tool Installations
Our approach is very similar to George's. We access the tools disk as R rather than P. We also have an SFS directory for local System Programmer tools. The latter does not include things we might need in an emergency; those go on a minidisk. We have another disk that is the common 191 for home grown service machines. It is accessed as B/A before the driver is started. All code written for the service machines goes on this disk. By doing this, we know where the code is when a server has trouble. There are a few good reasons for having the tools and common files on disk rather than SFS. One is that they are available even if SFS is down. This includes the time before SFS is initialized, the time you have SFS in dedicated maintenance mode (e.g. while increasing the size of the catalog minidisks), or it is down for some other reason. And for those who say that SFS is so reliable that its being down is of no concern, I say take off those rose colored glasses. We have had 2 major and one minor outage of SFS in the past 3 years. We were hamstrung for 2 days when the catalog was corrupted. This was following a datacenter migration - the disks were transferred via wire. The problem did not show up for 3 days. When it surfaced, it showed up as a CP abend. When we finally connected the repeated abends with SFS, we had to take the server down and send a copy of the catalog to the support center where a tailored zap was created that would, in essence, cause the server to skip over the corrupted catalog entries. This was an iterative process. After zapping the catalog, we were able to unload the filepool, generate a filepool using new disks, and reload the data to it. More recently, we have had to take the server down to increase the size of the catalog disks (twice). When we increased the size the first time, we underestimated how rapidly it would grow. SFS had been in use for several years and was fairly large at the time. We thought we were being generous when we gave the catalog 4 times the space that it occupied before. We were wrong. That only lasted about a year and a half. Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of George Haddad Sent: Monday, July 09, 2007 2:02 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Philosophy on Tool Installations Our philosophy has always been to leave the 19E/Y-disk for IBM. 3rd Party and homegrown public tools were put on our P-disk (public), 19A at MSU. A hook into SYSPROF accessed this for all users. (Sysprog tools were on a separate disk, as are Ops-only tools) Accessing our public disk at P meant that it was searched prior to the S or Y, so that we could put cover Execs and the like on it. Some tools (certain compilers and database software --- things with lots of individual files) were kept on their own disks, with front-end wrappers placed put on our P-disk to Link/Access/Execute those tools. These wrappers were 1-liner execs which called a generic table-lookup/link/access tool, also on our P-disk. Thus when changes we needed to the wrappers they could be done in a single executable. Stephen Frazier wrote: The answer is yes. A tool that is only needed by a few would be placed on its own mini-disk and linked to by those who need it. A tool that is used by almost everyone is placed on the Y disk so everyone has access to it all the time. [EMAIL PROTECTED] wrote: What is the best practice for installing tools into the z/VM space? 1. Do you create a mini-disk for each tool and have everyone who needs it link to that disk for the time needed to use the tool? 2. Do you create a common mini-disk that is accessed by every user? (in z/OS I would put the tools into their own libraries and then put those libraries into the linklist if everyone needed access or provide information on how to steplib for those infrequent uses). Thanks (and please forgive the mention of z/OS)
Re: Philosophy on Tool Installations
Our approach is very similar to George's. We access the tools disk as R rather than P. We also have an SFS directory for local System Programmer tools. The latter does not include things we might need in an emergency; those go on a minidisk. The method I've always favored is a variation of #2. We used to have a common minidisk (MAINT 31A for historical reasons) accessed as X (after S but before Y, so you get the real IBM utilities before the local stuff unless you explicitly ask for them) in SYSPROF EXEC. I then defined a target in VMLINK NAMES for each product I want to make available, which includes the location of the product (minidisk or SFS owner, directory, pre/post access setup execs, etc) and ensure the copy of VMLINK NAMES is updated on the X disk. I then supply a small cover exec that checks to see if the product disk has previously been accessed. If it has not been previously accessed, the cover exec does a VMLINK for the product (replacing an earlier home-grown exec called OBTAIN -- alas, OBTAIN, another lost tool with the death of RICEVM1...) and then reissues the command with the original parameter list. If it was already available, the cover exec just passed the parameters through to the real executable. This approach kept everything nice and neat, allowed a mixture of SFS and minidisk installs, and dealt nicely with the IBM stuff attempting to dump random stuff on MAINT 19E, which required a resave of the Y-STAT segment. Of course, this really matters a whole lot more if you have lots of CMS users. If all you have are a bunch of Linux guests with rare CMS sessions by well-behaved systems folks, just make 19E big and let the IBM execs dump stuff on there at will -- SES has improved enough to be able to sort stuff out properly for IBM-packaged goodies when you do your upgrades. A second minidisk accessed in either PROFILE EXEC or SYSPROF EXEC for your local goodies is still a good idea, though -- Mother's Law still applies. And for those who say that SFS is so reliable that its being down is of no concern, I say take off those rose colored glasses. Especially if you do not have a 3rd party backup utility and have to rely on FILESERV BACKUP as your SFS backup utility. Getting a truly clean backup of a SFS pool w/o 3rd party tooling is highly disruptive -- most CMS apps don't deal well with their disks suddenly going read-only without warning.
Re: How to determine if running as a multitasking CMS app
In case anyone's interested, I raised this with IBM. Their response was that testing NUCMTDSP wouldn't work, the only way possible being to run the CMS control blocks. Unfortunately, these control blocks have the note This information is NOT intended to be used as Programming Interfaces of z/VM ... which makes me a little uneasy about doing it this way. I guess it's all there is, though. From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Gillis, Mark Sent: Friday, 29 June 2007 11:07 PM To: IBMVM@LISTSERV.UARK.EDU Subject: How to determine if running as a multitasking CMS app I need to determine if my code is being called by a multitasking CMS program (i.e., with entrypoint VMSTART) or not. It seems that it is valid to issue almost any multitasking CMS call from a program that hasn't been linked as a multitasking CMS application, except for ThreadCreate and EventTrap, so at worst I could resort to issuing a ThreadCreate and check the results, but this seems to be a pretty expensive way to do it. I've noticed that the flag NUCMTDSP in the NUCON seems to be set when a multitasking CMS app is active. Does anyone know if there's a proper way to do this?
Re: How to determine if running as a multitasking CMS app
On Tuesday, 07/10/2007 at 10:16ZE10, Gillis, Mark [EMAIL PROTECTED] wrote: In case anyone?s interested, I raised this with IBM. Their response was that testing NUCMTDSP wouldn?t work, the only way possible being to run the CMS control blocks. Unfortunately, these control blocks have the note?This information is NOT intended to be used as Programming Interfaces of z/VM? ? which makes me a little uneasy about doing it this way. I guess it?s all there is, though. I have some assembler code that can run with C or Pascal (called prior to entering the real module). I put in a WXTRN for CEESTART and VSPASCAL in order to figure out whether it is running in an LE environment or not. Could you put in a WXTRN for VMSTART? If the adcon is non-zero, then VMSTART was linked. Alan Altmark z/VM Development IBM Endicott
Re: How to determine if running as a multitasking CMS app
Unfortunately, not applicable to what I'm doing - the module where I'm doing this is CMSCALL'd by a client application, so it's not linked in, and I need to maintain backward compatibility, so it needs to stay that way. Good idea, though. Mark Gillis Senior Software Engineer Tel: +61 2 9429 2337 Fax: +61 2 9429 2394 [EMAIL PROTECTED] -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: Tuesday, 10 July 2007 10:59 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: How to determine if running as a multitasking CMS app On Tuesday, 07/10/2007 at 10:16ZE10, Gillis, Mark [EMAIL PROTECTED] wrote: In case anyone?s interested, I raised this with IBM. Their response was that testing NUCMTDSP wouldn?t work, the only way possible being to run the CMS control blocks. Unfortunately, these control blocks have the note?This information is NOT intended to be used as Programming Interfaces of z/VM? ? which makes me a little uneasy about doing it this way. I guess it?s all there is, though. I have some assembler code that can run with C or Pascal (called prior to entering the real module). I put in a WXTRN for CEESTART and VSPASCAL in order to figure out whether it is running in an LE environment or not. Could you put in a WXTRN for VMSTART? If the adcon is non-zero, then VMSTART was linked. Alan Altmark z/VM Development IBM Endicott
Re: How to determine if running as a multitasking CMS app
Not sure if this will work but... Can you use DMSCALLER to look back to see who called you... do that repeatedly (looking further and further back) until you: A - find the origin of the universe you currently know or B - find VMSTART You would only need to do this one time when your program starts, then set your own flag for other parts to check as needed. Or (untested), try calling an MT function (that actually requires MT) if it works, you're MT; if not, you're not. (Might need an ESPIE or similar routine to catch an abend.) Gillis, Mark wrote: Unfortunately, not applicable to what I'm doing - the module where I'm doing this is CMSCALL'd by a client application, so it's not linked in, and I need to maintain backward compatibility, so it needs to stay that way. Good idea, though. Mark Gillis Senior Software Engineer Tel: +61 2 9429 2337 Fax: +61 2 9429 2394 [EMAIL PROTECTED] -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: Tuesday, 10 July 2007 10:59 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: How to determine if running as a multitasking CMS app On Tuesday, 07/10/2007 at 10:16ZE10, Gillis, Mark [EMAIL PROTECTED] wrote: In case anyone?s interested, I raised this with IBM. Their response was that testing NUCMTDSP wouldn?t work, the only way possible being to run the CMS control blocks. Unfortunately, these control blocks have the note?This information is NOT intended to be used as Programming Interfaces of z/VM? ? which makes me a little uneasy about doing it this way. I guess it?s all there is, though. I have some assembler code that can run with C or Pascal (called prior to entering the real module). I put in a WXTRN for CEESTART and VSPASCAL in order to figure out whether it is running in an LE environment or not. Could you put in a WXTRN for VMSTART? If the adcon is non-zero, then VMSTART was linked. Alan Altmark z/VM Development IBM Endicott
Re: How to determine if running as a multitasking CMS app
DMSCALLER returned the name of the calling load module - not VMSTART. Not to worry - running the chain of PSD's seems to work, I'll just keep my fingers crossed that it stays that way. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Don Russell Sent: Tuesday, 10 July 2007 11:29 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: How to determine if running as a multitasking CMS app Not sure if this will work but... Can you use DMSCALLER to look back to see who called you... do that repeatedly (looking further and further back) until you: A - find the origin of the universe you currently know or B - find VMSTART You would only need to do this one time when your program starts, then set your own flag for other parts to check as needed. Or (untested), try calling an MT function (that actually requires MT) if it works, you're MT; if not, you're not. (Might need an ESPIE or similar routine to catch an abend.) Gillis, Mark wrote: Unfortunately, not applicable to what I'm doing - the module where I'm doing this is CMSCALL'd by a client application, so it's not linked in, and I need to maintain backward compatibility, so it needs to stay that way. Good idea, though. Mark Gillis Senior Software Engineer Tel: +61 2 9429 2337 Fax: +61 2 9429 2394 [EMAIL PROTECTED] -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: Tuesday, 10 July 2007 10:59 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: How to determine if running as a multitasking CMS app On Tuesday, 07/10/2007 at 10:16ZE10, Gillis, Mark [EMAIL PROTECTED] wrote: In case anyone?s interested, I raised this with IBM. Their response was that testing NUCMTDSP wouldn?t work, the only way possible being to run the CMS control blocks. Unfortunately, these control blocks have the note?This information is NOT intended to be used as Programming Interfaces of z/VM? ? which makes me a little uneasy about doing it this way. I guess it?s all there is, though. I have some assembler code that can run with C or Pascal (called prior to entering the real module). I put in a WXTRN for CEESTART and VSPASCAL in order to figure out whether it is running in an LE environment or not. Could you put in a WXTRN for VMSTART? If the adcon is non-zero, then VMSTART was linked. Alan Altmark z/VM Development IBM Endicott
Re: How to determine if running as a multitasking CMS app
I'm not convinced that running the chain is the right solution. Sure, it names the caller(s), but that's hardly a programatic way to determine if you're in an MT environment. -- R; On Tue, 10 Jul 2007, Gillis, Mark wrote: DMSCALLER returned the name of the calling load module - not VMSTART. Not to worry - running the chain of PSD's seems to work, I'll just keep my fingers crossed that it stays that way. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Don Russell Sent: Tuesday, 10 July 2007 11:29 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: How to determine if running as a multitasking CMS app Not sure if this will work but... Can you use DMSCALLER to look back to see who called you... do that repeatedly (looking further and further back) until you: A - find the origin of the universe you currently know or B - find VMSTART You would only need to do this one time when your program starts, then set your own flag for other parts to check as needed. Or (untested), try calling an MT function (that actually requires MT) if it works, you're MT; if not, you're not. (Might need an ESPIE or similar routine to catch an abend.) Gillis, Mark wrote: Unfortunately, not applicable to what I'm doing - the module where I'm doing this is CMSCALL'd by a client application, so it's not linked in, and I need to maintain backward compatibility, so it needs to stay that way. Good idea, though. Mark Gillis Senior Software Engineer Tel: +61 2 9429 2337 Fax: +61 2 9429 2394 [EMAIL PROTECTED] -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: Tuesday, 10 July 2007 10:59 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: How to determine if running as a multitasking CMS app On Tuesday, 07/10/2007 at 10:16ZE10, Gillis, Mark [EMAIL PROTECTED] wrote: In case anyone?s interested, I raised this with IBM. Their response was that testing NUCMTDSP wouldn?t work, the only way possible being to run the CMS control blocks. Unfortunately, these control blocks have the note?This information is NOT intended to be used as Programming Interfaces of z/VM? ? which makes me a little uneasy about doing it this way. I guess it?s all there is, though. I have some assembler code that can run with C or Pascal (called prior to entering the real module). I put in a WXTRN for CEESTART and VSPASCAL in order to figure out whether it is running in an LE environment or not. Could you put in a WXTRN for VMSTART? If the adcon is non-zero, then VMSTART was linked. Alan Altmark z/VM Development IBM Endicott
Re: How to determine if running as a multitasking CMS app
On Mon, 9 Jul 2007, Alan Altmark wrote: I have some assembler code that can run with C or Pascal (called prior to entering the real module). I put in a WXTRN for CEESTART and VSPASCAL in order to figure out whether it is running in an LE environment or not. Could you put in a WXTRN for VMSTART? If the adcon is non-zero, then VMSTART was linked. I've made a note of your recommendation. But this still only tells us that VMSTART is in the mix. Someone please convince me that this is sufficient. -- R;
Re: Philosophy on Tool Installations
Lots of good responses to your question. VMLINK is so much better than OBTAIN which Dave Boyes mentioned. At most (all?) of the shops where I have worked, there has been at least some use of the minidisk-per-tool model, even a different minidisk for each release of a given tool or package. Record the VMID and minidisk address in VMLINK NAMES and it should work very smoothly. You can (should) write and EXEC to front-end the most relevant commands in the package so it is automatic and then put that on the 319 or 31A disk or some such. What I like about it is that it isolates the software as shipped from both user space and from other packages as well as from the O/S. (One of Melinda's rules: don't co-mingle the O/S and third party stuff.) Windows and Unix mess things up: They tend to install everything together. Windows at least now has C:\Program Files and Unix has /opt. But the implementation doesn't seem to be well understood. In Unix, there may be a wrapper or a sym-link in /usr/local/bin that enables each package, if they are not installed mixed together. Our wrapper EXECs on VM to do the link access part are similar. ADD TO ALL THIS the Unix (and Linux) concept of an automounter. Put tools on a disk or directory that is mounted on-the-fly, quite like we do things in VM land with link access on-the-fly. If more tools were installed this way, then upgrades would be much smoother. You could even let more than one release of a given software package co-exist on the same system. VMLINK is really slick. It robustly handles RELEASE and DETACH. Correlation to Unix is that automounter should unmount unused disks or directories. (It tries silently. Very nice.) -- R;
z/VM 5.3.0 BookManager Index is broken
Am I the only one who still uses BookManager/Read on VM? The index file (HCSH2A90 BKINDEX) for the z/VM V5R3.0 Bookshelf has a broken title. Today I used the IBM Softcopy Librarian to download the z/VM 5.3.0 BookManager manuals from the Internet. When I run the Bookmanager/Read fo r VM command: BOOKMGR * (SHELF I see: * Bookshelves Shelf Name Description ... HCSH2A90 /u/wooster/data/cmvc.d/CT_dummy.d/shelfinde when I should see: HCSH2A90 z/VM V5R3.0 Bookshelf or soemething similar. The same problem happened for the OSA/SF, EREP, and ICKDSF bookshelves in the last BookManager distribution. I reported this on IBMLink, but the ne w versions are still broken. All of the following now have gibberish titles : HCSH2A90 BKINDEX IOA2BK72 BKINDEX IFC5BK05 BKINDEX ICK41917 BKINDEX The last time, I rebuilt the three broken BKINDEX files from the BKSHELF files, using the INDEX EXEC that comes with BookManager/Read. I was able to rebuild three of them this time, but I cannot rebuild HCSH2A90 BKINDEX . I get: EIJIND920S EIJBOOK error 40 processing Index. EIJIND920S EIJBOOK error returncode processing command. Explanation: A critical error was generated by EIJBOOK when it tried t o perform the specified command. For example, if you do not have enough memory available the Index utility displays a return code of 38. If yo u do not have sufficient disk space the Index utility return code of 40 i s displayed. Perhaps I ran out of A-disk space? I created a 3338 cylinder A disk, but still got the message. I tried 16M, 128M, and 2047M virtaul machine sizes wiht the same results. Does anyone have any idea how where I can get or create a correct HCSH2A9 0 BKINDEX? I can opearte with only the BKSHELF file, and no BKINDEX, but then searching the bookshelf is horribly slow. I'm not sure what product I should open an incident to on IBMLink. My las t attempt cost me a lot of time with no solution provided.
