Dave:
I'm guessing the crux of the issue is ensuring completely unique numbers for
spooler
entries. In UD we use "BANNER UNIQUE" to append the user name to a date/time
stamp
and add ".txt" to the end (you know how stupid other software can be). We
pause for
a second to make sure no two entries have the same number. According to the
UniVerse
documentation:
BANNER [ name ]
In mode 1, a banner page is not produced unless the Windows printer has been
configured to do so. If you do not specify name, the Windows printer banner is
produced. If you specify name, it appears on the second line of the banner page,
after the user name. The banner name appears as the job name in the Windows
Print
Manager.
In mode 3, specifies the record ID of the record in &HOLD& which stores the
report.
If you do not specify name, the record ID is P#0000. If you specify name, it is
the
record ID of the output record. In either case, each subsequent print job uses
the
same record ID and overwrites the previous job.
BANNER NEXT [ name ]
In mode 3, appends a sequential number to the name under which successive
reports are
created in &HOLD&. If you do not specify name, the record ID is P#0000_nnnnnn,
where
nnnnnn is increased for each new print job. If you specify name, the record ID
is
name_nnnnnn.
BANNER UNIQUE [ name ]
In mode 3, appends a sequential number to the name under which successive
records are
created in &HOLD&. If you do not specify name, the record ID is P#0000_nnnnnn,
where
nnnnnn is increased by each subsequent SETPTR command. If you specify name, the
record ID is name_nnnnnn
...which indicates one can do the same thing by using just BANNER {name}. This
should provide enough capability to ensure each report is unique.
Have I misunderstood the OP's requirements?
Bill
>-----Original Message-----
>From: [EMAIL PROTECTED] [mailto:owner-u2-
>[EMAIL PROTECTED] On Behalf Of Dave Taylor
>Sent: Friday, August 15, 2008 4:33 PM
>To: u2-users@listserver.u2ug.org
>Subject: RE: [U2] Unidata to Universe port
>
>Jerry,
>
>Ref: Universe Rel. 10.1, Pick flavor account.
>
>Perhaps I didn't describe the limitation on the print entry numbers ("unique
>print file names") in Universe correctly, as I understand it.
>
>The Universe User Reference Guide describes the use of the &HOLD& file as
>follows:
>
>------
>&HOLD&
>
>Description
>
>&HOLD& is a local type 1 file used to hold spooled reports. If &HOLD& does
>not exist in the account, SETPTR(UNIX) or SETPTR (Windows Platforms) creates
>it when you use the SETPTR command to set a logical print channel to mode 3.
>Spooled reports to that channel become records in the &HOLD& file.
>
>Once a report has been sent to &HOLD&, you can edit, delete, or spool the
>report by using the Editor. The report remains in &HOLD& until you delete it
>or until another report with the same name is written to &HOLD&.
>
>The dictionary of &HOLD& contains a NEXT.HOLD record, which is an X-type
>item used by the spooler to create unique print file names. Field 2 of
>NEXT.HOLD contains a sequence number from 1 through 9999.
>
>In NLS mode, the spool queue directory holds data in UniVerse internal
>format. When data reaches the printer, it is mapped to an external character
>set using the appropriate map for the device. However, the default map
>associated with this file is NONE, unless the directory existed before you
>installed NLS. When you spool to a hold file, the spooler stores the data
>using the map associated with the &HOLD& directory. The data is then mapped
>again when it reaches the printer. For more information, see the UniVerse
>NLS Guide.
>-----
>
>If you edit the NEXT.HOLD item in the DICT &HOLD& file and set Field 2 =
>9999,
>it will look like this:
>
>>ED DICT &HOLD& NEXT.HOLD
>2 lines long.
>
>----:
>0001: X Next Available HOLD File Entry No.
>----:
>0002: 9999
>Bottom at line 2.
>----:
>
>If you then enter a SETPTR command with Mode = 3 and use the BANNER NEXT
>option,
>each subsequent print job will end in the number in Field 2 of the NEXT.HOLD
>dictionary record,
>incremented by 1 for each print job, and will restart numbering from 1 after
>it uses the number 9999,
>as illustrated in the following examples:
>
>
>
>LIST &HOLD& 04:04:34pm 15 Aug 2008 PAGE 1
>&HOLD&...
>
>UV^UVNT.SP
>OOLER^1^N^
>1_9999
>UV^UVNT.SP
>OOLER^1^N^
>1_1
>
>2 records listed.
>
>Unidata also has a default limitation on print numbers, but it can be
>expanded.
>
>IBM has told me that this unique print number can not be expanded in
>Universe.
>
>Do you get a different result than I do when you run the same test?
>
>How do you expand this 4-digit limitation in Universe beyond 9999?
>
>According to IBM, a number of others would also like to do this.
>
>Thanks,
>
>Dave
>
>Dave Taylor
>Sysmark Information Systems, Inc.
>Authorized IBM Business Partner
>49 Aspen Way
>Rolling Hills Estates, CA 90274
>(O) 800-SYSMARK (800-797-6275)
>(F) 310-377-3550
>(C) 310-561-5200
>www.sysmarkinfo.com
>----- Original Message -----
>From: "jpb-u2ug" <[EMAIL PROTECTED]>
>To: <u2-users@listserver.u2ug.org>
>Sent: Friday, August 15, 2008 7:44 AM
>Subject: [SPAM] RE: [U2] Unidata to Universe port
>
>
>> Dave,
>> Been a while since you've used UniVerse? The print job numbers are 6
>> digits.
>
><snip>
>-------
>u2-users mailing list
>u2-users@listserver.u2ug.org
>To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
