|
OK. I guess I've just been lucky all of these years when I've used *FCFC that all the spool files have been non-external. I have used *FCFC when the file I am CPYSPLFing will eventually be copied back to a print file (*FCFC is required when copying from a data file to a printer file like QPRINT). Still doesn't seem right, though. Have you tried using *FCFC on an external print file? (Maybe the docs are wrong.) Nevertheless, *PRTCTL should give you all the information you need for your purposes. SPLTOOL? What is it, $179? Heck, doesn't Sharper Image sell pens more expensive than that? ;-) But I agree with you on the thrill of reinventing something "in your own image". I've got a couple of ideas running right now and am shopping for AS/400 timeshare to keep from running into the ownership issues that have been conveniently debated in this very list for the past several days. I wanna be rich like Brad! - Dan Bale > -----Original Message----- > From: Joel Fritz [SMTP:JFritz@sharperimage.com] > Sent: Friday, May 26, 2000 5:37 PM > To: 'MIDRANGE-L@midrange.com' > Subject: RE: cpsplf *fcfc > > Actually, the HTML part is easy, depending on the degree of formatting. > For > presenting reports pretty much as they appear on paper, you have to insert > a > minimal set of tags. The underlining will appear (we've done that > already) > although not as nicely as true underlining. The problem (not an issue yet > for us) is externally defined print files. > > If you look in the CL Reference Manual, you'll see the following: > > " FCFC: The first character of every record contains an American National > Standards Institute (ANSI) forms control character. If *FCFC is > specified, > the record length must include one extra position for the first-character > forms-control code. This value is not valid for externally described > printer files. " > > BTW, SPLTOOL is a neat product. I've used it and like it. Selling > management on it is a different issue. (I know, it's not real expensive.) > There's also the perverse satisfaction that comes from reinventing the > wheel. (Mine is going to have unique wheel covers and iridescent tires. > <g>) > > -----Original Message----- > From: Bale, Dan [mailto:DBale@lear.com] > Sent: Friday, May 26, 2000 1:11 PM > To: 'MIDRANGE-L@midrange.com' > Subject: RE: cpsplf *fcfc > > > Under what context was the statement "*fcfc is not valid for externally > described printer files" made? > > If I'm understanding your post correctly, you want your HTML output to > have > the appropriate tags for underlining just like they appear in the printed > output? WYSIWYG? If this is what you're trying to do, you've got a LOT > of > work ahead of you. It's not just a simple matter of doing a CPYSPLF to a > database file to a PC file with inserted HTML tags. You will definately > need the *FCFC output to insert the appropriate HTML tags for underlining > and boldfacing. > > Of course, you could save yourself a lot of time & aggravation and get an > instant solution in Brad Stone's SPLTOOL product. > > hth, > - Dan Bale +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.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.