• Subject: Re: Re[2]: CHGPF Question
  • From: DAsmussen@xxxxxxx
  • Date: Fri, 19 Sep 1997 20:09:54 -0400 (EDT)


In a message dated 97-09-19 17:31:19 EDT, you write:

> >I disagree VEHEMENTLY with using LVLCHK(*NO) under ANY circumstances.
>  >make the same challenge that I did with GOTO -- show me a SINGLE example
>  >under which it would be valid, and I'll admit my mistake (haven't gotten 
> one
>  >in almost a year on GOTO yet, but you're welcome to try with LVLCHK)..
>  Please take this in the light humour I intend...
>  When using AFP objects like *PAGSEG or *OVERLAY, you use a PC to create
>  graphic, then you print through an AFP printer driver to a PC file.  You
> that
>  PC file in a /400 shared folder, then do a CPYFRMPCD to get it into a 
> physical
>  file on the /400.
>  THAT file MUST BE created LVLCHK(*NO) per IBM's instructions...
>  There's a *single* example under which it's valid.
>  (please don't hit me, I realise it's a very special circumstance, and not
>  really related to issues of database files in production, but I couldn't
>  resist...)

If I DID hit you, you'd not be able to reply and I'd hate THAT.  OK, but
cheating isn't allowed :-).  I meant DATABASE files!!


Dean Asmussen
Enterprise Systems Consulting, Inc.
Fuquay-Varina, NC  USA
E-Mail:  DAsmussen@AOL.COM

"Everywhere is walking distance if you have the time." -- Steven Wright
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].