Re: Determining file attributes *before* OPEN
In [EMAIL PROTECTED], on 10/07/2008 at 11:23 AM, John McKown [EMAIL PROTECTED] said: You'll need to get the volser that the dataset is on. If you simply have a DD, the RDJFCB will get the DSN. You'd then need to do a catalog lookup to find the volser. No, the volser is in the JFCB, so there's no need for the CSI or LOCATE unless there might be more than 5 volumes. BTW, I'd recommend using an ARL so that you can easily get attributes for concatenated data sets. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Determining file attributes *before* OPEN
In [EMAIL PROTECTED], on 10/07/2008 at 12:31 PM, Gerhard Postpischil [EMAIL PROTECTED] said: Unless they've been discontinued lately, try the LOCATE and CAMLST macros. ITYM OBTAIN and CAMLST. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Determining file attributes *before* OPEN
Indeed, that is all that I require at the moment. RDJFCB and OBTAIN do just what I needed. Peter -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Tom Marchant Sent: Tuesday, October 07, 2008 3:26 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Determining file attributes *before* OPEN On Tue, 7 Oct 2008 14:06:28 EDT, IBM Mainframe Discussion List [EMAIL PROTECTED] wrote: ... The only difference is which source (LOCATE or RDJFCB) will give you the complete volser list, if either. A complete list may not matter. For DSORG, RECFM, LRECL and BLKSIZE, the first volume should be sufficient. They should be the same on all volumes. 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 [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Determining file attributes *before* OPEN
Yes, this is what I have done and it works well. Since I only need information from the first volume (RECFM, LRECL, DSORG, etc.) the combination of TDJCB/X'13' and OBTAIN got me what I needed. I still need to do OBTAIN before the DD is first opened in the step in order to get the DSCB info. Otherwise the JFCB returned by RDJFCB contains only DSN and DISP for an existing dataset, which was the target here. Thanks for the help. Peter -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of David Kreiss Sent: Tuesday, October 07, 2008 2:18 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Determining file attributes *before* OPEN If you want all volume serial numbers use RDJFCB along with EXLST entry X'13' (EXARL in IHAEXLST) retrieve allocation information instead of entry X'07' (EXLRJFCB) and use IHAARL and IHAARA to map the ARL and ARA returned (the JFCB is in ARAJFCB). Dave Kreiss 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 [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Determining file attributes *before* OPEN
For DCB info I only need to do the OPTAIN for the first volume, so that is all I do now. I use the first volume from the RDJFCB/X'13' exit list, and that seems to do just what I need. No LOCATE necessary. Thanks for the help. Peter -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of (IBM Mainframe Discussion List) Sent: Tuesday, October 07, 2008 2:06 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Determining file attributes *before* OPEN Snipped Get the DSN from the RDJFCB. Then get the volsers from either the RDJFCB or the data returned via LOCATE. Plug each volser into the CAMLST that you use with OBTAIN, then do the OBTAIN to read the DSCB for each volume. Or use the volser from the RDJFCB data. The only difference is which source (LOCATE or RDJFCB) will give you the complete volser list, if either. 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 [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Determining file attributes *before* OPEN
I did take another look at those SVC 99 parameters, but nowhere in the Info Request parameters are any of the DCB fields that I was looking for (unless I missed them...?). Remember, this was a DD for an existing dataset, so no DCB info is typically coded in the JCL, just DISP and DSN. RDJFCB/X'13' and OBTAIN seem to do the trick though. Thanks for the advice anyway, it's always good to go back and look again at what you thought you already knew. Peter -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Rick Fochtman Sent: Tuesday, October 07, 2008 12:35 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Determining file attributes *before* OPEN You might want to check out the SVC-99 Information Request parameters. IIRC, you can point to a DD statement without opening the dataset. 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 [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Determining file attributes *before* OPEN
I have gone round and round with the manuals on this and I think I have the answer, but I just want to check my findings with others who have done similar things. These questions are for a normal z/OS LE/COBOL/Assembler non-authorized batch application environment not using Unix System Services or TSO/ISPF. AFAICT, the dead simplest way to determine basic file attributes (e.g., DSORG, RECFM, LRECL) for an allocated DD is to issue an OPEN and look at the DCB fields. The context here is for an *existing* DSN, not NEW where the JCL will have some or all of the info. Think DISP=SHR,DSN=my.dataset and nothing else on the DD statement. OPEN with a DCB is not such a good thing to do if the file is actually a VSAM file of any kind, but you can issue RDJFCB first and check the VSAM bit in JFCDSRG2 to see if it is VSAM or not. Then you can OPEN an ACB instead of a DCB and find out what you need. My primary question is whether there is a relatively simple, efficient way to determine basic file attributes for an allocated DD *before* issuing an OPEN. I know I can get basic file information with OPEN, but is there a way to do it *without* OPEN? My reading took me to CVAFDIR and company, but there are all sorts of restrictions there, not least of which is that unauthorized users must have a DEB address pointing to the volume that the DSCB resides on. The only non-authorized way to get a DEB seems to be to open a DCB pointing to the VTOC, which requires knowing the initial volume serial for the dataset, which at least requires RDJCFB with ARL-info returned, and an OPEN TYPE=J with a DCB open exit to change the DSN to all X'04', etc., etc. Way messy, and it requires an OPEN anyway. Using a different path, once I have the DSN via a RDJFCB then Catalog Search (IGGCSI00) can tell me if a file is VSAM or PS, but not what its RECFM or LRECL are (though I can get maximum LRECL for a VSAM file, but not for a PS file). The LE manuals seem to have nothing on file attributes that I could find, either regular or vendor-interface. So, besides actually issuing an OPEN, is there any non-authorized facility or service that would simply let me discover some basic file attributes for an allocated DD? And if OPEN is indeed the simplest way, I can accept that. I would just like to confirm that I haven't missed another way of accomplishing this task. TIA for any help/info/RTFM's you can provide. Peter 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 [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Determining file attributes *before* OPEN
Look at the OBTAIN macro for DASD resident datasets. http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/DGT2S341/1.3.2 You'll need to get the volser that the dataset is on. If you simply have a DD, the RDJFCB will get the DSN. You'd then need to do a catalog lookup to find the volser. I'd use the newest IGGCSI00 interface to do that instead of the old way (which I can't even remember what it is called - LOCATE?) -- John McKown -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Determining file attributes *before* OPEN
Farley, Peter x23353 wrote: So, besides actually issuing an OPEN, is there any non-authorized facility or service that would simply let me discover some basic file attributes for an allocated DD? You can use the OBTAIN macro (see DFSMSdfp Advanced Services) to read the DSCB. -- Richard -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Determining file attributes *before* OPEN
Farley, Peter x23353 wrote: So, besides actually issuing an OPEN, is there any non-authorized facility or service that would simply let me discover some basic file attributes for an allocated DD? Unless they've been discontinued lately, try the LOCATE and CAMLST macros. Gerhard Postpischil Bradford, VT -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Determining file attributes *before* OPEN
Look at the OBTAIN macro for DASD resident datasets. http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/DGT2S341/1.3.2 You'll need to get the volser that the dataset is on. If you simply have a DD, the RDJFCB will get the DSN. You'd then need to do a catalog lookup to find the volser. I'd use the newest IGGCSI00 interface to do that instead of the old way (which I can't even remember what it is called - LOCATE?) LOCATE and it still works fine. George Fogg -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Determining file attributes *before* OPEN
You might want to check out the SVC-99 Information Request parameters. IIRC, you can point to a DD statement without opening the dataset. Farley, Peter x23353 wrote: I have gone round and round with the manuals on this and I think I have the answer, but I just want to check my findings with others who have done similar things. These questions are for a normal z/OS LE/COBOL/Assembler non-authorized batch application environment not using Unix System Services or TSO/ISPF. AFAICT, the dead simplest way to determine basic file attributes (e.g., DSORG, RECFM, LRECL) for an allocated DD is to issue an OPEN and look at the DCB fields. The context here is for an *existing* DSN, not NEW where the JCL will have some or all of the info. Think DISP=SHR,DSN=my.dataset and nothing else on the DD statement. OPEN with a DCB is not such a good thing to do if the file is actually a VSAM file of any kind, but you can issue RDJFCB first and check the VSAM bit in JFCDSRG2 to see if it is VSAM or not. Then you can OPEN an ACB instead of a DCB and find out what you need. My primary question is whether there is a relatively simple, efficient way to determine basic file attributes for an allocated DD *before* issuing an OPEN. I know I can get basic file information with OPEN, but is there a way to do it *without* OPEN? My reading took me to CVAFDIR and company, but there are all sorts of restrictions there, not least of which is that unauthorized users must have a DEB address pointing to the volume that the DSCB resides on. The only non-authorized way to get a DEB seems to be to open a DCB pointing to the VTOC, which requires knowing the initial volume serial for the dataset, which at least requires RDJCFB with ARL-info returned, and an OPEN TYPE=J with a DCB open exit to change the DSN to all X'04', etc., etc. Way messy, and it requires an OPEN anyway. Using a different path, once I have the DSN via a RDJFCB then Catalog Search (IGGCSI00) can tell me if a file is VSAM or PS, but not what its RECFM or LRECL are (though I can get maximum LRECL for a VSAM file, but not for a PS file). The LE manuals seem to have nothing on file attributes that I could find, either regular or vendor-interface. So, besides actually issuing an OPEN, is there any non-authorized facility or service that would simply let me discover some basic file attributes for an allocated DD? And if OPEN is indeed the simplest way, I can accept that. I would just like to confirm that I haven't missed another way of accomplishing this task. TIA for any help/info/RTFM's you can provide. Peter 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 [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Determining file attributes *before* OPEN
Thanks John. Somehow I missed OBTAIN when I was browsing that manual. RDJFCB with an X'13' EXLST entry will return the first few volume serial numbers assigned to the dataset, so RDJFCB and OBTAIN would seem to be the way to go. -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of John McKown Sent: Tuesday, October 07, 2008 12:24 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Determining file attributes *before* OPEN Look at the OBTAIN macro for DASD resident datasets. http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/DGT2S341/1.3. 2 You'll need to get the volser that the dataset is on. If you simply have a DD, the RDJFCB will get the DSN. You'd then need to do a catalog lookup to find the volser. I'd use the newest IGGCSI00 interface to do that instead of the old way (which I can't even remember what it is called - LOCATE?) 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 [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Determining file attributes *before* OPEN
Thanks, I think that's what I'll be using. -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Richard Peurifoy Sent: Tuesday, October 07, 2008 12:23 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Determining file attributes *before* OPEN Farley, Peter x23353 wrote: So, besides actually issuing an OPEN, is there any non-authorized facility or service that would simply let me discover some basic file attributes for an allocated DD? You can use the OBTAIN macro (see DFSMSdfp Advanced Services) to read the DSCB. 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 [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Determining file attributes *before* OPEN
Thanks, but LOCATE/CAMLST only returns a volume list, not D(S)CB attributes. I can get the first few volumes from RDJFCB as well, along with the DSN, and that's enough info to use OBTAIN (which I missed the first time around) to get the DSCB. -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Gerhard Postpischil Sent: Tuesday, October 07, 2008 12:32 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Determining file attributes *before* OPEN Farley, Peter x23353 wrote: So, besides actually issuing an OPEN, is there any non-authorized facility or service that would simply let me discover some basic file attributes for an allocated DD? Unless they've been discontinued lately, try the LOCATE and CAMLST macros. 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 [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Determining file attributes *before* OPEN
I called myself looking at those parameters, but perhaps I missed something. I will look again. Thanks. -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Rick Fochtman Sent: Tuesday, October 07, 2008 12:35 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Determining file attributes *before* OPEN You might want to check out the SVC-99 Information Request parameters. IIRC, you can point to a DD statement without opening the dataset. 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 [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Determining file attributes *before* OPEN
In a message dated 10/7/2008 12:02:05 P.M. Central Daylight Time, [EMAIL PROTECTED] writes: Thanks, but LOCATE/CAMLST only returns a volume list, not D(S)CB attributes. I can get the first few volumes from RDJFCB as well, along with the DSN, and that's enough info to use OBTAIN (which I missed the first time around) to get the DSCB. Get the DSN from the RDJFCB. Then get the volsers from either the RDJFCB or the data returned via LOCATE. Plug each volser into the CAMLST that you use with OBTAIN, then do the OBTAIN to read the DSCB for each volume. Or use the volser from the RDJFCB data. The only difference is which source (LOCATE or RDJFCB) will give you the complete volser list, if either. Bill Fairchild Rocket Software **New MapQuest Local shows what's happening at your destination. Dining, Movies, Events, News more. Try it out (http://local.mapquest.com/?ncid=emlcntnew0002) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Determining file attributes *before* OPEN
If you want all volume serial numbers use RDJFCB along with EXLST entry X'13' (EXARL in IHAEXLST) retrieve allocation information instead of entry X'07' (EXLRJFCB) and use IHAARL and IHAARA to map the ARL and ARA returned (the JFCB is in ARAJFCB). Dave Kreiss -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of (IBM Mainframe Discussion List) Sent: Tuesday, October 07, 2008 11:06 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Determining file attributes *before* OPEN In a message dated 10/7/2008 12:02:05 P.M. Central Daylight Time, [EMAIL PROTECTED] writes: Thanks, but LOCATE/CAMLST only returns a volume list, not D(S)CB attributes. I can get the first few volumes from RDJFCB as well, along with the DSN, and that's enough info to use OBTAIN (which I missed the first time around) to get the DSCB. Get the DSN from the RDJFCB. Then get the volsers from either the RDJFCB or the data returned via LOCATE. Plug each volser into the CAMLST that you use with OBTAIN, then do the OBTAIN to read the DSCB for each volume. Or use the volser from the RDJFCB data. The only difference is which source (LOCATE or RDJFCB) will give you the complete volser list, if either. Bill Fairchild Rocket Software **New MapQuest Local shows what's happening at your destination. Dining, Movies, Events, News more. Try it out (http://local.mapquest.com/?ncid=emlcntnew0002) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Determining file attributes *before* OPEN
(IBM Mainframe Discussion List) wrote: Get the DSN from the RDJFCB. Then get the volsers from either the RDJFCB or the data returned via LOCATE. Plug each volser into the CAMLST that you use with OBTAIN, then do the OBTAIN to read the DSCB for each volume. Or use the volser from the RDJFCB data. The only difference is which source (LOCATE or RDJFCB) will give you the complete volser list, if either. One nice change in HDZ1A10: you can obtain multiple DSCBs at once. -- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA 90045 310-338-0400 x318 [EMAIL PROTECTED] http://www.phoenixsoftware.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Determining file attributes *before* OPEN
On Tue, 7 Oct 2008 14:06:28 EDT, IBM Mainframe Discussion List [EMAIL PROTECTED] wrote: ... The only difference is which source (LOCATE or RDJFCB) will give you the complete volser list, if either. A complete list may not matter. For DSORG, RECFM, LRECL and BLKSIZE, the first volume should be sufficient. They should be the same on all volumes. -- Tom Marchant -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
