Re: most jobs abended with 878-04 after upgrade CPU from 2964 to 2094 (HELP)
Tommy Tsui wrote: hi all, we found that many jobs abended with 878-04 after upgrade CPU from 2064 to 2094 (first day batch) . There are no error when runnng on 2064 machine. any shop have this problem?? Is there any control-block changed after upgrade CPU??/ any comment will be appreciated You didn't mention whether any software changes were concurrent with the upgrade. Typically, at least some supporting PTFs are installed for a server upgrade, and often other configuration changes are made concurrently. Both can affect the virtual storage map and lead to what you see. In addition to added code in PTFs, which can move the NUCLEUS and LPA boundaries, some modules are loaded into the nucleus only when the configuration requires them, which can likewise move the NUCLEUS's upper and lower ending boundaries, but I've no clue whether that could or does apply to your particular configuration change. Got an RMF report that shows the storage boundaries from before, and one from after? No? How about a dump from which you can find and/or format the GDA (Global Data Area)? Basically, you want to look at the amount of CSA and ECSA before and after in addition to the amount of SQA and ESQA before and after, and, I suspect, figure out what to specify to regain adequately-sized storage areas. Note that (E)SQA allocation requests will be satisfied from (E)SQA if available, and from (E)CSA afterward if necessary. To be unable to satisfy the allocation request, you have effectively run out of both. The (E)CSA areas are ended on segment (1 MB) boundaries, and that can add considerably to the amount of available (E)CSA you specify. In the event that the sizes of other storage areas (Nucleus, FLPA/PLPA/MLPA/LPA, SQA) conspire to move the end of your (E)CSA specifications closer to their nearest 1 MB boundaries, the amount of available space can be reduced considerably. The worst case is to *just* cross one going in the wrong direction (toward the 16 MB line in both cases), in which case you can lose nearly 1 MB of CSA, ECSA, or both. You should be cognizant of your virtual storage map, and periodically adjust your (E)CSA specifications to plant the end of both *specified* areas somewhere near the middle of two segment boundaries. This will generally keep day-to-day changes from making you cross a boundary unaware, helping prevent surprises. In my opinion, doing this as part of migrating to each new release is a good idea and likely to be adequate most of the time. However, I have not tested this assumption in a production environment in over 15 years, and your mileage may vary. This topic from Init & Tuning might be helpful, too: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/iea2e280/49.8?ACTION=MATCHES&REQUEST=csa&TYPE=FUZZY&SHELF=EZ2ZO10j&DT=20070516223132&CASE=&searchTopic=TOPIC&searchText=TEXT&searchIndex=INDEX&rank=RANK&ScrollTOP=FIRSTHIT#FIRSTHIT -- John Eells z/OS Technical Marketing IBM Poughkeepsie [EMAIL PROTECTED] -- 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: most jobs abended with 878-04 after upgrade CPU from 2964 to 2094 (HELP)
Tommy Tsui wrote: > our current setting on IEASYSXX > SQA=(6,8M), > CSA=(1600,4) > > real memory increase from 1G to 2G after upgrade from 2064 to 2094 > > > Our SQA setting in IEASYS00 is : SQA=(12,45M). With the other ESQA that gets automatically added at NIP/IPL time we are running with a 60M ESQA which is currently 56% used. IMHO your ESQA setting is way too low. > > On 2/19/08, Tommy Tsui <[EMAIL PROTECTED]> wrote: > >> only I do that is increase the real memory from 1G to 2G. Is there any >> problem here >> >> >> >> On 2/19/08, Staller, Allan <[EMAIL PROTECTED]> wrote: >> >>> >>> we found that many jobs abended with 878-04 after upgrade CPU from >>> 2064 to >>> 2094 (first day batch) . There are no error when runnng on 2064 >>> machine. any >>> shop have this problem?? Is there any control-block changed after upgrade CPU??/ >>> >>> >>> Default region? Check (in roughly descending order) >>> JES init deck, >>> SMFPRMxx >>> IEFUJI(exit) >>> IEFUSI(exit) >>> Additional datasets in LPALSTxx. >>> >>> Did you increase real storage significantly. SQA usage increases with >>> additional real storage and reduces the private area available >>> >>> >>> HTH, >>> >>> -- >>> 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 > > -- Mark Jacobs Time Customer Service Tampa, FL The dogmas of the quiet past are inadequate to the stormy present. The occasion is piled high with difficulty, and we must rise to the occasion. We cannot escape history. We will be remembered in spite of ourselves. The fiery trial through which we pass will light us down in honor or dishonor, to the last generation. Abraham Lincoln -- 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: most jobs abended with 878-04 after upgrade CPU from 2964 to 2094 (HELP)
Another interesting question, I changed this setting to 3 LPARs (from 1GB to 2GB real memory), but no job abended on another two LPARs. The other two LPARs with same SQA & ESQA setting with default region size 1M. On 2/19/08, Tommy Tsui <[EMAIL PROTECTED]> wrote: > > so, do you mean that additional ESQA required after 1G real memory > adding? but why I have no problem when I adding 2GB to our development lpar > with no change to ESQA??? > > > > On 2/19/08, Tom Marchant <[EMAIL PROTECTED]> wrote: > > > > On Mon, 18 Feb 2008 12:52:45 -0600, Tom Marchant wrote: > > > > > > > >Page Frame Tables are in ESQA, one 64 byte entry for every 4K byte > > page. > > > > Correction. PFTEs are now in a data space. Ignore what I said above. > > > > -- > > 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 > > > > -- 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: most jobs abended with 878-04 after upgrade CPU from 2964 to 2094 (HELP)
so, do you mean that additional ESQA required after 1G real memory adding? but why I have no problem when I adding 2GB to our development lpar with no change to ESQA??? On 2/19/08, Tom Marchant <[EMAIL PROTECTED]> wrote: > > On Mon, 18 Feb 2008 12:52:45 -0600, Tom Marchant wrote: > > > > >Page Frame Tables are in ESQA, one 64 byte entry for every 4K byte page. > > Correction. PFTEs are now in a data space. Ignore what I said above. > > -- > 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 > -- 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: most jobs abended with 878-04 after upgrade CPU from 2964 to 2094 (HELP)
On Mon, 18 Feb 2008 12:52:45 -0600, Tom Marchant wrote: > >Page Frame Tables are in ESQA, one 64 byte entry for every 4K byte page. Correction. PFTEs are now in a data space. Ignore what I said above. -- 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
Re: most jobs abended with 878-04 after upgrade CPU from 2964 to 2094 (HELP)
On Tue, 19 Feb 2008 02:35:35 +0800, Tommy Tsui wrote: >our current setting on IEASYSXX >SQA=(6,8M), >CSA=(1600,4) > >real memory increase from 1G to 2G after upgrade from 2064 to 2094 As John pointed out, your abends are for SP 248, which is ESQA. Page Frame Tables are in ESQA, one 64 byte entry for every 4K byte page. If my arithmetic is correct, another 1 GB of memory will require an additional 16 MB of ESQA. -- 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
Re: most jobs abended with 878-04 after upgrade CPU from 2964 to 2094 (HELP)
Tommy Tsui wrote: > This is a good idea but some of our job even code region=4M but also > abended. > The subpool in the error message indicates ESQA getmain failures. Altering the REGION on the jobcard or JES2 option won't have any effect. > On 2/19/08, Staller, Allan <[EMAIL PROTECTED]> wrote: > >> >> ... but some of our job does not code the region size on job step that >> means it will use the default. In our JES2 parm, the default region size >> is 1M. >> >> >> This is most likely your problem. >> 1) change jobclass definitions in JES init deck >> 2) Issue $TJOBCLASS(*),REGION=4M (required). >> >> 4M is a suggestion. It can be anything you installation decides is >> reasonable. >> >> Is it not enough to restart JES to pick up the changes. The $TJOBCLASS >> must be issued. BTDTGTTS. >> >> -- >> 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 > > -- Mark Jacobs Time Customer Service Tampa, FL The dogmas of the quiet past are inadequate to the stormy present. The occasion is piled high with difficulty, and we must rise to the occasion. We cannot escape history. We will be remembered in spite of ourselves. The fiery trial through which we pass will light us down in honor or dishonor, to the last generation. Abraham Lincoln -- 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: most jobs abended with 878-04 after upgrade CPU from 2964 to 2094 (HELP)
This is a good idea but some of our job even code region=4M but also abended. On 2/19/08, Staller, Allan <[EMAIL PROTECTED]> wrote: > > > ... but some of our job does not code the region size on job step that > means it will use the default. In our JES2 parm, the default region size > is 1M. > > > This is most likely your problem. > 1) change jobclass definitions in JES init deck > 2) Issue $TJOBCLASS(*),REGION=4M (required). > > 4M is a suggestion. It can be anything you installation decides is > reasonable. > > Is it not enough to restart JES to pick up the changes. The $TJOBCLASS > must be issued. BTDTGTTS. > > -- > 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: most jobs abended with 878-04 after upgrade CPU from 2964 to 2094 (HELP)
... but some of our job does not code the region size on job step that means it will use the default. In our JES2 parm, the default region size is 1M. This is most likely your problem. 1) change jobclass definitions in JES init deck 2) Issue $TJOBCLASS(*),REGION=4M (required). 4M is a suggestion. It can be anything you installation decides is reasonable. Is it not enough to restart JES to pick up the changes. The $TJOBCLASS must be issued. BTDTGTTS. -- 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: most jobs abended with 878-04 after upgrade CPU from 2964 to 2094 (HELP)
I know this is a dif sub but also be careful if you are using OSA , we had a lot of trouble from 2064 - 2094 because IBM changed mach code Brian Peterson IBM-MAIN@BAMA.UA.EDU Sent by: IBM cc Mainframe Discussion List Subject <[EMAIL PROTECTED] Re: most jobs abended with 878-04 .EDU> after upgrade CPU from 2964 to 2094 (HELP) 02/18/2008 01:24 PM Please respond to IBM Mainframe Discussion List <[EMAIL PROTECTED] .EDU> On Tue, 19 Feb 2008 02:11:27 +0800, Tommy Tsui wrote: >hi all, > >we found that many jobs abended with 878-04 after upgrade CPU from 2064 to >2094 (first day batch) . There are no error when runnng on 2064 machine. any >shop have this problem?? >Is there any control-block changed after upgrade CPU??/ > >any comment will be appreciated > >Many thanks > >tommy Perhaps on your 2064, your DASD devices were defined LOCANY YES and on the 2094 they're defined LOCANY NO? Parameter/ FeatureValueR Description LOCANY YesUCB can reside in 31 bit storage Brian -- 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: most jobs abended with 878-04 after upgrade CPU from 2964 to 2094 (HELP)
our current setting on IEASYSXX SQA=(6,8M), CSA=(1600,4) real memory increase from 1G to 2G after upgrade from 2064 to 2094 On 2/19/08, Tommy Tsui <[EMAIL PROTECTED]> wrote: > > only I do that is increase the real memory from 1G to 2G. Is there any > problem here > > > > On 2/19/08, Staller, Allan <[EMAIL PROTECTED]> wrote: > > > > > > > we found that many jobs abended with 878-04 after upgrade CPU from > > 2064 to > > > 2094 (first day batch) . There are no error when runnng on 2064 > > machine. any > > > shop have this problem?? > > > Is there any control-block changed after upgrade CPU??/ > > > > > > Default region? Check (in roughly descending order) > > JES init deck, > > SMFPRMxx > > IEFUJI(exit) > > IEFUSI(exit) > > Additional datasets in LPALSTxx. > > > > Did you increase real storage significantly. SQA usage increases with > > additional real storage and reduces the private area available > > > > > > HTH, > > > > -- > > 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: most jobs abended with 878-04 after upgrade CPU from 2964 to 2094 (HELP)
only I do that is increase the real memory from 1G to 2G. Is there any problem here On 2/19/08, Staller, Allan <[EMAIL PROTECTED]> wrote: > > > > we found that many jobs abended with 878-04 after upgrade CPU from > 2064 to > > 2094 (first day batch) . There are no error when runnng on 2064 > machine. any > > shop have this problem?? > > Is there any control-block changed after upgrade CPU??/ > > > Default region? Check (in roughly descending order) > JES init deck, > SMFPRMxx > IEFUJI(exit) > IEFUSI(exit) > Additional datasets in LPALSTxx. > > Did you increase real storage significantly. SQA usage increases with > additional real storage and reduces the private area available > > > HTH, > > -- > 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: most jobs abended with 878-04 after upgrade CPU from 2964 to 2094 (HELP)
Tommy Tsui wrote: > just like this message > IEA705I ERROR DURING GETMAIN SYS CODE = 878-04 PXXJOB16 PBUGALT 00 > IEA705I 00FB3400 009DFCF0 009DFCF0 00F87200 0398 > IEA705I ERROR DURING GETMAIN SYS CODE = 878-04 PXXJOB16 PBUGALT 00 > IEA705I 00FB3400 009DFCF0 009DFCF0 00F87200 0398 > IEF450I PXXJOB16 PBUGALT - ABEND=S878 U REASON=0004 866 > > after the abended, the operator re-run the same job with no error. > Even this IDCAMS backup REPRO job are abended with 878-04 > > thanks > Subpool 248 (F8) is for ESQA allocations. Did the size of your ESQA virtual storage map change between machine's? > On 2/19/08, Tommy Tsui <[EMAIL PROTECTED]> wrote: > >> hi all, >> >> we found that many jobs abended with 878-04 after upgrade CPU from 2064 to >> 2094 (first day batch) . There are no error when runnng on 2064 machine. any >> shop have this problem?? >> Is there any control-block changed after upgrade CPU??/ >> >> any comment will be appreciated >> >> Many thanks >> >> tommy >> >> > > -- > 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 > > -- Mark Jacobs Time Customer Service Tampa, FL The dogmas of the quiet past are inadequate to the stormy present. The occasion is piled high with difficulty, and we must rise to the occasion. We cannot escape history. We will be remembered in spite of ourselves. The fiery trial through which we pass will light us down in honor or dishonor, to the last generation. Abraham Lincoln -- 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: most jobs abended with 878-04 after upgrade CPU from 2964 to 2094 (HELP)
I check with the IODF definition. All device are already in LOCANY YES, but some of our job does not code the region size on job step that means it will use the default. In our JES2 parm, the default region size is 1M. On 2/19/08, Brian Peterson <[EMAIL PROTECTED]> wrote: > > On Tue, 19 Feb 2008 02:11:27 +0800, Tommy Tsui wrote: > > >hi all, > > > >we found that many jobs abended with 878-04 after upgrade CPU from 2064 > to > >2094 (first day batch) . There are no error when runnng on 2064 machine. > any > >shop have this problem?? > >Is there any control-block changed after upgrade CPU??/ > > > >any comment will be appreciated > > > >Many thanks > > > >tommy > > Perhaps on your 2064, your DASD devices were defined LOCANY YES and on > the 2094 they're defined LOCANY NO? > > Parameter/ > FeatureValueR Description > LOCANY YesUCB can reside in 31 bit storage > > Brian > > -- > 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: most jobs abended with 878-04 after upgrade CPU from 2964 to 2094 (HELP)
> we found that many jobs abended with 878-04 after upgrade CPU from 2064 to > 2094 (first day batch) . There are no error when runnng on 2064 machine. any > shop have this problem?? > Is there any control-block changed after upgrade CPU??/ Default region? Check (in roughly descending order) JES init deck, SMFPRMxx IEFUJI(exit) IEFUSI(exit) Additional datasets in LPALSTxx. Did you increase real storage significantly. SQA usage increases with additional real storage and reduces the private area available HTH, -- 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: most jobs abended with 878-04 after upgrade CPU from 2964 to 2094 (HELP)
On Tue, 19 Feb 2008 02:11:27 +0800, Tommy Tsui wrote: >hi all, > >we found that many jobs abended with 878-04 after upgrade CPU from 2064 to >2094 (first day batch) . There are no error when runnng on 2064 machine. any >shop have this problem?? >Is there any control-block changed after upgrade CPU??/ > >any comment will be appreciated > >Many thanks > >tommy Perhaps on your 2064, your DASD devices were defined LOCANY YES and on the 2094 they're defined LOCANY NO? Parameter/ FeatureValueR Description LOCANY YesUCB can reside in 31 bit storage Brian -- 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: most jobs abended with 878-04 after upgrade CPU from 2964 to 2094 (HELP)
just like this message IEA705I ERROR DURING GETMAIN SYS CODE = 878-04 PXXJOB16 PBUGALT 00 IEA705I 00FB3400 009DFCF0 009DFCF0 00F87200 0398 IEA705I ERROR DURING GETMAIN SYS CODE = 878-04 PXXJOB16 PBUGALT 00 IEA705I 00FB3400 009DFCF0 009DFCF0 00F87200 0398 IEF450I PXXJOB16 PBUGALT - ABEND=S878 U REASON=0004 866 after the abended, the operator re-run the same job with no error. Even this IDCAMS backup REPRO job are abended with 878-04 thanks On 2/19/08, Tommy Tsui <[EMAIL PROTECTED]> wrote: > > hi all, > > we found that many jobs abended with 878-04 after upgrade CPU from 2064 to > 2094 (first day batch) . There are no error when runnng on 2064 machine. any > shop have this problem?? > Is there any control-block changed after upgrade CPU??/ > > any comment will be appreciated > > Many thanks > > tommy > -- 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: most jobs abended with 878-04 after upgrade CPU from 2964 to 2094 (HELP)
Tommy Tsui wrote: > hi all, > > we found that many jobs abended with 878-04 after upgrade CPU from 2064 to > 2094 (first day batch) . There are no error when runnng on 2064 machine. any > shop have this problem?? > Is there any control-block changed after upgrade CPU??/ > > any comment will be appreciated > > Many thanks > > tommy > > What subpool was identified in the associated error message? -- Mark Jacobs Time Customer Service Tampa, FL The dogmas of the quiet past are inadequate to the stormy present. The occasion is piled high with difficulty, and we must rise to the occasion. We cannot escape history. We will be remembered in spite of ourselves. The fiery trial through which we pass will light us down in honor or dishonor, to the last generation. Abraham Lincoln -- 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
most jobs abended with 878-04 after upgrade CPU from 2964 to 2094 (HELP)
hi all, we found that many jobs abended with 878-04 after upgrade CPU from 2064 to 2094 (first day batch) . There are no error when runnng on 2064 machine. any shop have this problem?? Is there any control-block changed after upgrade CPU??/ any comment will be appreciated Many thanks tommy -- 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
