|
Thanks. I'll double check, but i'm pretty sure this is the case. The file is created with the proper characters. It's when we read the file and write it to the IFS (via RPG program) that the DBCS data gets corrupted (there is other SBCS data in the spooled file as well). On Fri, 05 May 2006 09:15:59 +0800 Vengoal Chang <vengoal@xxxxxxxxxxx> wrote: > 1. You must make sure your job ccsid is 937 and your > system enable DBCS > feature 2984, if your system is SBCS, your CRTPF command > does not have > IGCDTA parameter, and you cannot cpysplf with DBCS char > in SBCS system. > > 2. If your job ccsid is 937 and DBCS enabled. > CRTPF QTEMP/SPOOL220 RCDLEN(220) IGCDTA(*YES) > CPYSPLF > > If your job ccsid is 65535, or DBCS not enabled you > need create PF > with a DDS source like following: > A R SPLR > A SPLDTA 220 O <== field O type > CRTPF QGPL/SPOOL220 source(xxx/SPOOL220) > CPYSPLF > > it should be work. > > > Best regards, > > Vengoal > > > -------- Original Message -------- > From: "Brad Stone" <brad@xxxxxxxxxxxx> > To: Midrange Systems Technical Discussion > <midrange-l@xxxxxxxxxxxx> > Subject: Re:DBCS and the IFS > Date: 2006/5/4 ?? 09:50 > > >Still no dice... :( > > > >What I'm going to try is to get a copy of the file and > try > >it on another machine. > > > >I did notice something in the job log (since the PF is > >being populated with CPYSPLF) > > > >CPF3468 Diagnostic 40 05/04/06 11:12:19.242392 QSPCPYF > QSYS > >0734 S2X001CL SPLTOOL 00A6 > >Message . . . . : Double-byte data detected in spooled > file > >ACP270O not > >correct. > > > >I'm not sure if this is CPYSPLF saying "I can't do this" > or > >if it's saying the DBCS data in the spooled file is in > >error. But it appears when we look at the file that it > is > >fine. > > > >On Wed, 03 May 2006 22:35:38 -0500 > > "Brad Stone" <brad@xxxxxxxxxxxx> wrote: > > > > > >>Vengoal, > >> > >>Thanks so much for this. This is what I had suggested > to > >>the user earlier, to change their job to 937 and then > >>specify 950 as the ASCII code page (which is I believe > >>what > >>you described). > >> > >>When I saw the job's CCSID, it kind of clicked why > things > >>weren't working since it was a 37 code page for the > job, > >>yet trying to convert DBCS data from a completely > >>different > >>character set. > >> > >>Again, many thanks for your help and suggestions! > >> > >>Brad > >> > >> > >>On Thu, 04 May 2006 08:36:08 +0800 > >> Vengoal Chang <vengoal@xxxxxxxxxxx> wrote: > >> > >> > >>>Brad, > >>> > >>>When your system CCSID is 65535, and your languageID > is > >>>37, all job's > >>>default ccsid is 37. > >>>If you want to use system default text translation > will > >>>use ASCII 819 as > >>>client code page.(for example CPYFRMSTMF, CPYFRMIMPF, > >>>CPYTOSTMF, > >>>CPYTOIMPF ..., or C API open, write with option > >>>create,codepage, O_TEXT..) > >>> > >>>you could not specfy 950 as a system or job ccsid, you > >>>need set your job > >>>ccsid as 937. > >>>You have two option to converting to client code page > >>>950. > >>>1. run job ccsid as 937, and PF File CCSID as 937, run > >>>system command > >>>(above list command), this forced the system use > >>>937<-->950 mapping, but > >>>this is limited to external descript PF with DDS field > >>>type O or J. If > >>>you create a temp PF with CRTPF (xxx) RCDLEN(nnn) > >>>IGCDTA(*YES) under Job > >>>CCSID 65535, the temp PF's CCSID still is 37, and you > >>> > >>> > >>use > >> > >> > >>>the file doing > >>>converting under FTP or other CPYTOxxx, CPYFRMxxx, you > >>>will get the > >>>mapping error. > >>> > >>>2. Use API CDRCVRT to convert PF data, don't care waht > >>>ever CCSID in PF > >>>or STMF. This method bypass the system ccsid or job > >>>ccsid. But use this > >>>method with FTP put to PC file, remember use binary > >>> > >>> > >>mode > >> > >> > >>>to transfer it. > >>>Or use the samba client to put and get file from PC > >>>share(samba client > >>>installation step reference > >>> > >>> > >>> > >http://www.iseriesnetwork.com/isnetforums/showthread.php?t=42978&highlight=samba > > > > > >>>Best regards, > >>> > >>>Vengoal > >>> > >>>-------- Original Message -------- > >>>From: "Brad Stone" <brad@xxxxxxxxxxxx> > >>>To: Midrange Systems Technical Discussion > >>><midrange-l@xxxxxxxxxxxx> > >>>Subject: Re:DBCS and the IFS > >>>Date: 2006/5/3 ?? 10:44 > >>> > >>> > >>> > >>>>I'm opening it with the CCSID specified, that part > has > >>>>always worked. We're trying 950 as the CCSID. > >>>> > >>>>I also thought about the job CCSID and default CCSID > >>>> > >>>> > >>as > >> > >> > >>>>these are used to create the PF that is used, read > in, > >>>> > >>>> > >>>and > >>> > >>> > >>>>converted to an IFS file. > >>>> > >>>>The user has 65535 as the job CCSID and 37 as the > >>>> > >>>> > >>>default > >>> > >>> > >>>>CCSID. > >>>> > >>>>I though because his job CCSID was not 937 (or even > >>>> > >>>> > >>the > >> > >> > >>>>CHRID system value), this created the file used with > a > >>>>CCSID of his job, then trying to convert that CCSID > to > >>>> > >>>> > >>>937 > >>> > >>> > >>>>could be the issue. > >>>> > >>>>Maybe? > >>>> > >>>>On Wed, 3 May 2006 08:57:35 -0500 > >>>>Bruce Vining <bvining@xxxxxxxxxx> wrote: > >>>> > >>>> > >>>> > >>>> > >>>>>What is your open statement? What release are you > on > >>>>>(prior to V5R1 would > >>>>>be a problem)? What is your job CCSIDand job > default > >>>>>CCSID (in case you > >>>>>don't have O_CCSID specified with an explicit > value)? > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>>"Brad Stone" <brad@xxxxxxxxxxxx> > >>>>>Sent by: midrange-l-bounces@xxxxxxxxxxxx > >>>>>05/03/2006 08:50 AM > >>>>>Please respond to > >>>>>Midrange Systems Technical Discussion > >>>>><midrange-l@xxxxxxxxxxxx> > >>>>> > >>>>> > >>>>>To > >>>>>Midrange Systems Technical Discussion > >>>>><midrange-l@xxxxxxxxxxxx> > >>>>>cc > >>>>> > >>>>>Subject > >>>>>Re: DBCS and the IFS > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>>Sorry, that should have read "opening the stream > >>>>> > >>>>> > >>file", > >> > >> > >>>>>not > >>>>>spooled file.. :) > >>>>> > >>>>>On Wed, 03 May 2006 08:08:53 -0500 > >>>>>"Brad Stone" <brad@xxxxxxxxxxxx> wrote: > >>>>> > >>>>> > >>>>> > >>>>> > >>>>>>I'm getting a "conversion error" message when > trying > >>>>>> > >>>>>> > >>>to > >>> > >>> > >>>>>>open the spooled file with 950 as the code page. > >>>>>> > >>>>>> > >>> Would > >>> > >>> > >>>>>>it > >>>>>>make a difference on V5R2? > >>>>>> > >>>>>>Brad > >>>>>> > >>>>>>On Tue, 02 May 2006 23:17:12 -0500 > >>>>>>"Brad Stone" <brad@xxxxxxxxxxxx> wrote: > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>>>Thanks, Vengoal. > >>>>>>> > >>>>>>>We will give this a shot! > >>>>>>> > >>>>>>>Brad > >>>>>>> > >>>>>>>On Wed, 03 May 2006 08:33:32 +0800 > >>>>>>>Vengoal Chang <vengoal@xxxxxxxxxxx> wrote: > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>>>Traditional Chinese DBCS iSeries CCSID: 937 > >>>>>>>>mapping to client ASCII is 950. You need change > >>>>>>>> > >>>>>>>> > >>IFS > >> > >> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>ccsid > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>>>by CHGATR > >>>>>>>>change IFS STMF ccsid to 950. > >>>>>>>> > >>>>>>>> > >>>>>>>>When you use FTP to put binary file to iSeries > >>>>>>>> > >>>>>>>> > >>the > >> > >> > >>>>>>>>default iSeries > >>>>>>>>CCSID is 819, but if you use quote type c 950, > you > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>will > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>>>>get ccsid 950 STMF. > >>>>>>>>When you copy file from PC to iSeries under > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>NetServer > >>>>> > >>>>> > >>>>> > >>>>> > >>>>>>>>share or using > >>>>>>>>samba client copy pc shared file from iSeries, > you > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>will > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>>>>get ccsid 1208 > >>>>>>>>or 1252. You also need manual changet to STMF > 950. > >>>>>>>> > >>>>>>>> > >>>>>>>>Best regards, > >>>>>>>> > >>>>>>>>Vengoal > >>>>>>>> > >>>>>>>>-------- Original Message -------- > >>>>>>>>From: Bruce Vining <bvining@xxxxxxxxxx> > >>>>>>>>To: Midrange Systems Technical Discussion > >>>>>>>><midrange-l@xxxxxxxxxxxx> > >>>>>>>>Subject: Re:DBCS and the IFS > >>>>>>>>Date: 2006/5/2 ?? 11:44 > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>>>Brad, > >>>>>>>>> > >>>>>>>>>If you have Chinese characters that you are > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>attempting > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>>>>to convert then 937 > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>>>is the better way to go. 1175 is a proper > subset > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>of > >>>>> > >>>>> > >>>>> > >>>>> > >>>>>>>the > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>>>characters found > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>>>in CCSID 37 (CHRID 697 37) and contains no > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>Traditional > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>>>>Chinese characters. > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>>>937 contains the 1175 character set plus the > DBCS > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>935 > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>>>>character set. You > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>>>will also want to convert to a CCSID other than > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>819 > >>>>> > >>>>> > >>>>> > >>>>> > >>>>>>as > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>>>>that's just ISO > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>>>Latin 1 (again no Traditional Chinese). > >>>>>>>>> > >>>>>>>>>Bruce > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>>"Brad Stone" <brad@xxxxxxxxxxxx> > >>>>>>>>>Sent by: midrange-l-bounces@xxxxxxxxxxxx > >>>>>>>>>05/02/2006 09:40 AM > >>>>>>>>>Please respond to > >>>>>>>>>Midrange Systems Technical Discussion > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>><midrange-l@xxxxxxxxxxxx> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>>>To > >>>>>>>>>Midrange Systems Technical Discussion > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>><midrange-l@xxxxxxxxxxxx> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>>>cc > >>>>>>>>> > >>>>>>>>>Subject > >>>>>>>>>Re: DBCS and the IFS > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>>Thanks Bruce. > >>>>>>>>> > >>>>>>>>>It shows the CCSID to use for ASCII (if I'm > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>reading > >>>>> > >>>>> > >>>>> > >>>>> > >>>>>>it > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>>>>>right) is 819, but there seems to be some > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>traditional > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>>>>>chinese characters that don't get converted > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>properly > >>>>> > >>>>> > >>>>> > >>>>> > >>>>>>>>from > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>>>EBCDIC to ASCII. > >>>>>>>>> > >>>>>>>>>Brad > >>>>>>>>> > >>>>>>>>> > >>>>>>>>>On Tue, 2 May 2006 08:53:12 -0500 > >>>>>>>>>Bruce Vining <bvining@xxxxxxxxxx> wrote: > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>>>Brad, > >>>>>>>>>> > >>>>>>>>>>If you go to the V5R4 Information Center and > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>search > >>>>> > >>>>> > >>>>> > >>>>> > >>>>>>>on > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>>>>>1175 you will find > >>>>>>>>>>that 1175 is the default CHRID for the English > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>Upper > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>>>>and > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>>>>Lower Case DBCS > >>>>>>>>>>NLV (2984) and the SBCS CHRID for CCSID 937 > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>(Traditional > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>>>>Chinese). > >>>>>>>>>> > >>>>>>>>>>Bruce Vining > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>>"Brad Stone" <brad@xxxxxxxxxxxx> > >>>>>>>>>>Sent by: midrange-l-bounces@xxxxxxxxxxxx > >>>>>>>>>>05/02/2006 08:11 AM > >>>>>>>>>>Please respond to > >>>>>>>>>>Midrange Systems Technical Discussion > >>>>>>>>>><midrange-l@xxxxxxxxxxxx> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>>To > >>>>>>>>>>Midrange Systems Technical Discussion > >>>>>>>>>><midrange-l@xxxxxxxxxxxx> > >>>>>>>>>>cc > >>>>>>>>>> > >>>>>>>>>>Subject > >>>>>>>>>>DBCS and the IFS > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>>I am working with a customer who is running > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>QCHRID > >>>>> > >>>>> > >>>>> > >>>>> > >>>>>>>1175 > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>>>>>and > >>>>>>>>>>having problems with DBCS conversion from > EBCDIC > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>to > >>>>> > >>>>> > >>>>> > >>>>> > >>>>>>>>ASCII > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>>>>while writing to the IFS. > >>>>>>>>>> > >>>>>>>>>>I can normally find what CCSID to use in the > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>conversion > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>>>>>in > >>>>>>>>>>the IBM documentation, but in this case I find > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>little > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>>>>>>mention of this CHRID in any tables. > >>>>>>>>>> > >>>>>>>>>>Anyone familiar? I believe it's a traditional > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>Chinese > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>>>>>character set. > >>>>>>>>>> > >>>>>>>>>>Thanks! > >>>>>>>>>>-- > >>>>>>>>>>This is the Midrange Systems Technical > >>>>>>>>>> > >>>>>>>>>> > >>Discussion > >> > >> > >>>>>>>>>>(MIDRANGE-L) mailing > >>>>>>>>>>list > >>>>>>>>>>To post a message email: > MIDRANGE-L@xxxxxxxxxxxx > >>>>>>>>>>To subscribe, unsubscribe, or change list > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>options, > >>>>> > >>>>> > >>>>> > >>>>> > >>>>>>>>>>visit: > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>http://lists.midrange.com/mailman/listinfo/midrange-l > >>>>>> > >>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>>>>or email: MIDRANGE-L-request@xxxxxxxxxxxx > >>>>>>>>>>Before posting, please take a moment to review > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>the > >>>>> > >>>>> > >>>>> > >>>>> > >>>>>>>>>>archives > >>>>>>>>>>at http://archive.midrange.com/midrange-l. > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>>-- > >>>>>>>>>>This is the Midrange Systems Technical > >>>>>>>>>> > >>>>>>>>>> > >>Discussion > >> > >> > >>>>>>>>>>(MIDRANGE-L) mailing list > >>>>>>>>>>To post a message email: > MIDRANGE-L@xxxxxxxxxxxx > >>>>>>>>>>To subscribe, unsubscribe, or change list > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>options, > >>>>> > >>>>> > >>>>> > >>>>> > >>>>>>>>>>visit: > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>http://lists.midrange.com/mailman/listinfo/midrange-l > >>>>>> > >>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>>>>or email: MIDRANGE-L-request@xxxxxxxxxxxx > >>>>>>>>>>Before posting, please take a moment to review > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>the > >>>>> > >>>>> > >>>>> > >>>>> > >>>>>>>>>>archives > >>>>>>>>>>at http://archive.midrange.com/midrange-l. > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>> > >>>>>>>>>Bradley V. Stone > >>>>>>>>>BVS.Tools > >>>>>>>>>www.bvstools.com > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>-- > >>>>>>>>This is the Midrange Systems Technical Discussion > >>>>>>>>(MIDRANGE-L) mailing list > >>>>>>>>To post a message email: MIDRANGE-L@xxxxxxxxxxxx > >>>>>>>>To subscribe, unsubscribe, or change list > options, > >>>>>>>>visit: > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>http://lists.midrange.com/mailman/listinfo/midrange-l > >>>>> > >>>>> > >>>>> > >>>>> > >>>>>>>>or email: MIDRANGE-L-request@xxxxxxxxxxxx > >>>>>>>>Before posting, please take a moment to review > the > >>>>>>>>archives > >>>>>>>>at http://archive.midrange.com/midrange-l. > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>Bradley V. Stone > >>>>>>>BVS.Tools > >>>>>>>www.bvstools.com > >>>>>>>-- > >>>>>>>This is the Midrange Systems Technical Discussion > >>>>>>>(MIDRANGE-L) mailing list > >>>>>>>To post a message email: MIDRANGE-L@xxxxxxxxxxxx > >>>>>>>To subscribe, unsubscribe, or change list options, > >>>>>>>visit: > >>>>>>> > >>>>>>> > >>>>>>http://lists.midrange.com/mailman/listinfo/midrange-l > >>>>>> > >>>>>> > >>>>>>>or email: MIDRANGE-L-request@xxxxxxxxxxxx > >>>>>>>Before posting, please take a moment to review the > >>>>>>>archives > >>>>>>>at http://archive.midrange.com/midrange-l. > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>Bradley V. Stone > >>>>>>BVS.Tools > >>>>>>www.bvstools.com > >>>>>>-- > >>>>>>This is the Midrange Systems Technical Discussion > >>>>>>(MIDRANGE-L) mailing list > >>>>>>To post a message email: MIDRANGE-L@xxxxxxxxxxxx > >>>>>>To subscribe, unsubscribe, or change list options, > >>>>>>visit: > >>>>>> > >>>>>> > >>>>>http://lists.midrange.com/mailman/listinfo/midrange-l > >>>>> > >>>>> > >>>>>>or email: MIDRANGE-L-request@xxxxxxxxxxxx > >>>>>>Before posting, please take a moment to review the > >>>>>>archives > >>>>>>at http://archive.midrange.com/midrange-l. > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>Bradley V. Stone > >>>>>BVS.Tools > >>>>>www.bvstools.com > >>>>>-- > >>>>>This is the Midrange Systems Technical Discussion > >>>>>(MIDRANGE-L) mailing > >>>>>list > >>>>>To post a message email: MIDRANGE-L@xxxxxxxxxxxx > >>>>>To subscribe, unsubscribe, or change list options, > >>>>>visit: > >>>>>http://lists.midrange.com/mailman/listinfo/midrange-l > >>>>>or email: MIDRANGE-L-request@xxxxxxxxxxxx > >>>>>Before posting, please take a moment to review the > >>>>>archives > >>>>>at http://archive.midrange.com/midrange-l. > >>>>> > >>>>> > >>>>>-- > >>>>>This is the Midrange Systems Technical Discussion > >>>>>(MIDRANGE-L) mailing list > >>>>>To post a message email: MIDRANGE-L@xxxxxxxxxxxx > >>>>>To subscribe, unsubscribe, or change list options, > >>>>>visit: > >>>>>http://lists.midrange.com/mailman/listinfo/midrange-l > >>>>>or email: MIDRANGE-L-request@xxxxxxxxxxxx > >>>>>Before posting, please take a moment to review the > >>>>>archives > >>>>>at http://archive.midrange.com/midrange-l. > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>Bradley V. Stone > >>>>BVS.Tools > >>>>www.bvstools.com > >>>> > >>>> > >>>> > >>>> > >>>-- > >>>This is the Midrange Systems Technical Discussion > >>>(MIDRANGE-L) mailing list > >>>To post a message email: MIDRANGE-L@xxxxxxxxxxxx > >>>To subscribe, unsubscribe, or change list options, > >>>visit: > >>>http://lists.midrange.com/mailman/listinfo/midrange-l > >>>or email: MIDRANGE-L-request@xxxxxxxxxxxx > >>>Before posting, please take a moment to review the > >>>archives > >>>at http://archive.midrange.com/midrange-l. > >>> > >>> > >>> > >>Bradley V. Stone > >>BVS.Tools > >>www.bvstools.com > >>-- > >>This is the Midrange Systems Technical Discussion > >>(MIDRANGE-L) mailing list > >>To post a message email: MIDRANGE-L@xxxxxxxxxxxx > >>To subscribe, unsubscribe, or change list options, > >>visit: > >>http://lists.midrange.com/mailman/listinfo/midrange-l > >>or email: MIDRANGE-L-request@xxxxxxxxxxxx > >>Before posting, please take a moment to review the > >>archives > >>at http://archive.midrange.com/midrange-l. > >> > >> > >> > > > >Bradley V. Stone > >BVS.Tools > >www.bvstools.com > > > > > -- > This is the Midrange Systems Technical Discussion > (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: > http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the > archives > at http://archive.midrange.com/midrange-l. > Bradley V. Stone BVS.Tools www.bvstools.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.