printer file "name" - problem

[Dennis Malen]

Laura,

I do have your Quick Reference Guide and also find it a handy reference.

Your explanation of umask was great. I finally understand it, although I 
don't think I need it in my processing (unless you insist) as the file is 
being written to the /tmp file, although not correctly without modifications 
that I should not have to make (explained below).

In conclusion, I think you are saying my processing code is correct.

I will go back and try it again but the two problems I was initially having 
with this code are:

1. It would not over ride the defined printer in the report format. I solved 
that by copying over the report and not defining a printer (shouldn't have 
to do that);

2. When I copied the report over so there was no interference with any 
defined printer (since there was none) the file created was composed of each 
record being written and then adding 63 blank lines (definition of the page 
length was 64) and wrote the next page in a similar fashion. Pulling 93 
records creating 93 pages scrolling through the screen. When I defined the 
length of the page as 1 (as opposed to 64), it then printed correctly on the 
screen.

So I am really back to square one from my initial post.

Dennis

----- Original Message ----- 
From: "Laura Brody" <laura at hvcomputer.com>
To: "Dennis Malen" <dmalen at malen.com>; "filePro mailing list" 
<filepro-list at seaslug.org>
Sent: Thursday, March 17, 2005 3:46 PM
Subject: Re: printer file "name" - problem


> On Thu, 17 Mar 2005 14:39:10 -0500, Dennis Malen <dmalen at malen.com> wrote:
>
>> Brian,
>>
>> I reviewed your comments and I find that my processing has everything you 
>> suggested except for :
>>
>> system noredraw "umask 0;>"<fn
>>
>> Is this line necessary and why?
>
> Yes.
>
> Explanation of umask from Linux Magazine:
> <http://64.233.161.104/search?q=cache:BMHScth6Pg0J:www.linux-magazine.com/issue/27/fstab.pdf+umask+0+description&hl=en>
>
> The umask option in this entry has not been discussed previously. As Table 
> 2
> shows, the option sets inverse file privileges. What does that mean? Just
> like the chmod command, umask works with octal numbers. The access bits 
> are
> calculated by subtracting the desired file privileges from seven, and 
> assigning the
> result as the umask.
>
> The access privileges for the modes read, write and execute (octal 7) are 
> thus
> assigned by entering 0, r-x (octal 5) by entering 2, and rw- (octal 6) by 
> typing a
> 1. As Windows 98 does not support access privileges for files, we can use
> Linux access bits to impose an extra level of security.
> In this case we are applying fairly lax security privileges, since umask=0
> will allow any user to read, write and execute any file. You can type man
> -P ?less +?/^[ ]*umask?? bash for additional information on using masked
> file privileges.
>
>> I still need the PUTENV, as I only want the heading to be printed once.
>
> No problem with this command.
>
>> I am only executing that command once, unless it doesn't matter. I do 
>> know that PRINTER FILE (per Ken) must only be executed once. I'm not 
>> clear on whether PRINTER TYPE needs to be only once. If someone would 
>> clarify that, it would be appreciated.
>
> I don't know if multiple executions of PRINTER TYPE would mess
> things up, but I would only execute it once.
>
>> Once I get this clarified I will post the final results on what works. It 
>> is evident that this is not clear to everyone. This is what the list is 
>> all about.
>
> I think that it would be helpful to you if you knew
> the filePro printer hierarchy.... (which can be found on page 83
> of "Laura's Quick Reference Guide for filePro version 5.0, 2nd edition")
>
> 1) PRINTER command in processing (type and dest)
>
> 2) Command line flags
> -p  (dest)
> -PC (type)
> -PN (type and dest)
> -PQ (type and dest)
> -PT (dest)
> -PV (dest)
>
> 3) Output format options (type and dest) --- you are using this and
> can override it with 1) or 2).
>
> 4) Environmental variables
>
> 5) Default printer as defined in Printer Maintenance or
> PFPRINTER enviromental variable.
>
> Defaults: (if none of the above)
> DOS: default PRN
> UNIX/Linux: default "lp -s"
>
> -- 
> Laura Brody, Publisher of the filePro Developer's Journal
> +------------- Hudson Valley Computer Associates, Inc ----------+
> | PO Box 859 120 Sixth Street    http://www.hvcomputer.com      |
> | Verplanck, NY 10596-0859       Voice mail: (914) 739-5004     |
> +------ PC repair locally, filePro programming globally --------+
>
>
>
>