RE: Printer file positioning

A fair question John.

The way I've always viewed it is that the BOXes, LINEs, etc. are being written much like an artist paints on a canvas. Place a BOX here, put a LINE there, and so forth - without skipping or spacing. The POS values tend to write the BOX/LINE (positionally) exactly where you tell them too.

The 2nd, more traditional record, prints in mroe traditional ways - SPACEB, SKIPA, etc. Print a value or values, etc.

Bill

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of John McKee
Sent: Tuesday, February 10, 2009 5:10 PM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Printer file positioning


This sounds like a dumb question to me. But, it is bugging me anyway.

Program has two WRITEs in it, one for each record in the printer file.
Seems to
work great. But why does it work properly? I get a single page from the
printer, which is exactly what I want. Why didn't two WRITEs produce two
pages? I am not using anything on either record to defer writing.

Which brings up the alternate question: If two forms are printed, what would
put them on separate pages? Is there some timing issue here?

I'll bet this goes back to some fundamental DDS concept. But, the reason I
thought I had to put the BOX keyword on the same record format was to prevent
multiple pages being printed.

John McKee

Quoting Bill Reger <BillR@xxxxxxxxxxxxxx>:

Yeah John, works pretty good. What I've seen is to reserve one
record format for all the fixed stuff - like BOXes, LINEs, things
like that. And then a second (more traditional) record formnat for
all the variable data.

Bill

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of John McKee
Sent: Tuesday, February 10, 2009 4:01 PM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Printer file positioning


Guess I was making it too hard. Added the second record and it is so
slick. THANKS!

John McKee

Quoting "Scott, Bill" <Bill.Scott@xxxxxxx>:

Simply put the BOX command on a different record, then you do not
have to change everything to POSITION. I usually use "normal" spacing
for the detail lines of the invoice/packing list, whatever and just
use POSITION when you absolutely have to have perfect placement.


Bill Scott
Océ North America, Inc.
Tel.: (561) 997-3256
e-mail: Bill.Scott@xxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John McKee
Sent: Tuesday, February 10, 2009 1:28
To: Midrange Systems Technical Discussion
Subject: Printer file positioning

Just completed work on the first printer file I have built from
scratch in over twenty years.

I saw a nice keyword, BOX. I wanted to use this to surround a
portion of the report. But, using that keyword requires that
POSITION be used on all other entries.

What I don't understand is that, from what I have read, that the
values used for POSITION are related to the UOM at the time the
printer file is created.
Problem is I was attempting to convert row/column to position values.
PDM complains when it sees POSITION(10 60). So, obviously, PDM is
not looking at the row column UOM, but is defaulting to inches.

The way I read the manual, it is possible to specify row and column.
Is that correct? If so, how do I get PDM to not complain? I don't
see anything in the options that effects how the syntax checker
interprets values supplied to the POSITION keyword.

John McKee

--
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 message and attachment(s) are intended solely for use by the
addressee and may contain information that is privileged,
confidential or otherwise exempt from disclosure under applicable law.

If you are not the intended recipient or agent thereof responsible
for delivering this message to the intended recipient, you are hereby
notified that any dissemination, distribution or copying of this
communication is strictly prohibited.

If you have received this communication in error, please notify the
sender immediately by telephone and with a 'reply' message.

Thank you for your co-operation.


--
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.

--
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.