Re: [U2] Unidata to Universe port
I would stick to your core reason for a topic of discussion first before discussing all the differences and what's involved in migrating. We have had somewhat limited exposure trying to implement NLS for a few of our end users and were not successful in the past. The product may have been enhanced since then but I would be curious to hear from anyone who has successfully implemented this within UniVerse. The reason I bring this up is this seems to be the key motivating factor and if this is taken away, the point becomes mute. Regards, Doug At 08:41 PM 8/14/2008, you wrote: The reason we're even considering this is because of IBM's decision not to implement NLS in UniData, at least not right away. Of course, we've had conversations with IBM about converting, but would appreciate hearing from any one who has actually done this. --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] Unidata to Universe port
The problem is that both Dave and I have spooler products that try to intercept the output and direct it to a HOLD file. This involves using an interlude to the SP.ASSIGN/SETPTR verb. Many times, this only gets executed once per login. While we both have developed work-arounds to this issue, expanding that number from has been requested FOR YEARS. One UV product manager even thought it had already been done. We've been asking for this to be corrected for almost a decade, but the request falls on deaf ears. Fer gods sake, it's not Rocket Science! It would take, what, 2 hours to code and one automated regression run to verify? Regards, Clif -- W. Clifton Oliver, CCP CLIFTON OLIVER ASSOCIATES Tel: +1 619 460 5678Web: www.oliver.com On Aug 15, 2008, at 9:20 PM, JPB-U2UG wrote: I didn't realize you were referring to the HOLD file. In that case you are correct about the numbers being only 4 digits. However, you can expand the usage by giving the hold entries names as well as numbers by using the BANNER option. Here is from the manual: --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] Unidata to Universe port
Bill, and Clif and Jerry, Yes. Basically, you're correct. We do use the BANNER UNIQUE and the BANNER NEXT options for our Unidata and Universe installations, respectively. One of our two examples, UV^UVNT.SPOOLER^1^N^1_, shows a label that contains the Login ID, Account Name,Queue No., Print Options (Null in this case), No. of Copies and the Print Job No. assigned by Universe appended to the end. We check each record in the HOLD/_HOLD_ file periodically (default = 2 sec.) and, if it has been written completely to the file, add print status codes and a time-date stamp in seconds to the item id, copy it to our own hold file and delete it from the HOLD/_HOLD_ file. This assures that no subsequent record overwrites an existing record with the same print job number that may still be on hold in our hold file. But, it doesn't preclude the possibility of having two records on hold with the same print job number, and that can be confusing to the user who identifies a particular print job by that print job number. Since we do control the item id of each print job in our hold file, we could actually intercept the original print job number and re-scale it to any number of digits we wish when we rebuild the item id. One of our customers has already done that and it works fine for them. It's on our enhancement list for the next customer who asks for it. I think that Clif could do this with his spooler product also. Thank you all for your suggestions. Best wishes always, 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: Bill Haskett [EMAIL PROTECTED] To: u2-users@listserver.u2ug.org Sent: Friday, August 15, 2008 7:28 PM Subject: RE: [U2] Unidata to Universe port 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: snip --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Unidata to Universe port
Hi The biggest thing will be to choose what flavour to run your universe accounts in, this will affect how similar any TCL and dictionary items will be. As far as the unibasic extensions these are coded to be the same on both udt and uv. Rgds Symeon -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eugene St. Clair Sent: 15 August 2008 02:42 To: u2-users@listserver.u2ug.org Subject: [U2] Unidata to Universe port Hello: Does any one have any experiences they would be willing to share regarding the effort required to port applications from UniData to Universe? We're currently on Unidata 7.1 We developed our application in an early version of SB+ and UniBasic and have kept current on SB+, so we're now at version 5.4. We've also made use of various connectivity technolgies over time, such as ODBC, OLEDB, and UniObjects. We haven't used the web services or ADO provider yet, but probably will eventually. We are currently running on Windows but a Unix flavor is not out of the question if there is a compelling reason. At this point, I'm just trying to figure out a way to gauge the relative effort, and if there were any surprises, such as better/worse performance, costs, development effort, etc and of course, any gotchas. Also, is it feasible to to code the application in a way that it would work on either platform from the same code base? The reason we're even considering this is because of IBM's decision not to implement NLS in UniData, at least not right away. Of course, we've had conversations with IBM about converting, but would appreciate hearing from any one who has actually done this. thanks in advance. Eugene --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.138 / Virus Database: 270.6.3/1612 - Release Date: 14/08/2008 18:03 --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] Unidata to Universe port
If you are truly SB (i.e. You have coded all your fields and screens etc. in that environment) then conversion shouldn't be that hard. Fields can be regenerated using SB and so your main issues could be incompatibilities in basic code. Things like using as a variable name something that is OK in UniVerse but a reserved word in UniData. We recently took an SB application from UniVerse to UniData for a client and it took a couple of days including physically transporting the system. You certainly can code in such a way as to be able to run on both platforms, the difficulty is purely in knowing what is compatible with what. Unfortunately I don't think anyone has ever done a guide to what the common ground is. Depending on the size of the application I'd recommend spending a few days and trying it. Some things, like recompiling all your programs, don't take long but do mean that you can find the extent of the problem fairly easily. George Land APT Solutions Ltd U2 UK Master Distributor On 15/08/2008 02:41, Eugene St. Clair [EMAIL PROTECTED] wrote: Hello: Does any one have any experiences they would be willing to share regarding the effort required to port applications from UniData to Universe? We're currently on Unidata 7.1 We developed our application in an early version of SB+ and UniBasic and have kept current on SB+, so we're now at version 5.4. We've also made use of various connectivity technolgies over time, such as ODBC, OLEDB, and UniObjects. We haven't used the web services or ADO provider yet, but probably will eventually. We are currently running on Windows but a Unix flavor is not out of the question if there is a compelling reason. At this point, I'm just trying to figure out a way to gauge the relative effort, and if there were any surprises, such as better/worse performance, costs, development effort, etc and of course, any gotchas. Also, is it feasible to to code the application in a way that it would work on either platform from the same code base? The reason we're even considering this is because of IBM's decision not to implement NLS in UniData, at least not right away. Of course, we've had conversations with IBM about converting, but would appreciate hearing from any one who has actually done this. thanks in advance. Eugene --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify us immediately on +44 (01952) 214000 or at [EMAIL PROTECTED] . Please delete and destroy any copies in any format of this email you may have received in error. The recipient should note that the views contained or expressed within this correspondence do not necessarily reflect those of APT Solutions Limited , it subsidiaries, affiliates or associates. This email and any attachments are not guaranteed to be free from so-called computer viruses and it is recommended that you check for such viruses before down-loading it to your computer equipment. It is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message or any attachments will not adversely affect their systems or data. Registered Office:- Stratum House, Stafford Park 10, Telford, Shropshire, TF3 3AB Registration Number:- 2228445 Place of Registration: England Wales ** --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Unidata to Universe port
Dave, Been a while since you've used UniVerse? The print job numbers are 6 digits. I have worked on both Unidata and UniVerse and depending on the flavor used the dictionary's can be the same. Since Eugene has been developing with SB+ more than likely he has been using the Pick flavor which would run well on the Universe Pick or Reality flavors. Unidata does have V dictionary items but Universe has I dictionary items which work the same. I think there use to be a conversion program. Jerry Banker -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Taylor Sent: Thursday, August 14, 2008 11:57 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] Unidata to Universe port Eugene, I'm sure others will have a longer list, but for starters: 1.The structure of dictionary items is completely different. 2.You lose the ability to expand the print job numbers beyond before they restart numbering print jobs at 1 in UniVerse. Best wishes, 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: Eugene St. Clair [EMAIL PROTECTED] To: u2-users@listserver.u2ug.org Sent: Thursday, August 14, 2008 6:41 PM Subject: [U2] Unidata to Universe port Hello: Does any one have any experiences they would be willing to share regarding the effort required to port applications from UniData to Universe? 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/
RE: [U2] Unidata to Universe port
When I started working with UniVerse 7 years ago, the main gotcha I ran into was this. INS '' BEFORE VAL1,POS At that time, this worked on all the UniData systems I'd previously worked on but does not work here on UniVerse. We do this to get around it. VAL1,1 = :@VM:VAL1 I am assuming that this occurs on all UniVerse systems but may just be a parameter setup here. I am also assuming that it still works on UniData. Brenda Price --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Unidata to Universe port
Just realized I typo'd make that VAL1 = :@VM:VAL1. Sorry! -Original Message- From: Brenda Price [mailto:[EMAIL PROTECTED] Sent: Friday, August 15, 2008 10:07 AM To: u2-users@listserver.u2ug.org Subject: RE: [U2] Unidata to Universe port When I started working with UniVerse 7 years ago, the main gotcha I ran into was this. INS '' BEFORE VAL1,POS At that time, this worked on all the UniData systems I'd previously worked on but does not work here on UniVerse. We do this to get around it. VAL1,1 = :@VM:VAL1 I am assuming that this occurs on all UniVerse systems but may just be a parameter setup here. I am also assuming that it still works on UniData. Brenda Price --- 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/
Re: [U2] Unidata to Universe port
Yes, George you are correct. We use Pick flavor. - Original Message From: jpb-u2ug [EMAIL PROTECTED] To: u2-users@listserver.u2ug.org Sent: Friday, August 15, 2008 9:44:15 AM Subject: RE: [U2] Unidata to Universe port Dave, Been a while since you've used UniVerse? The print job numbers are 6 digits. I have worked on both Unidata and UniVerse and depending on the flavor used the dictionary's can be the same. Since Eugene has been developing with SB+ more than likely he has been using the Pick flavor which would run well on the Universe Pick or Reality flavors. Unidata does have V dictionary items but Universe has I dictionary items which work the same. I think there use to be a conversion program. Jerry Banker -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Taylor Sent: Thursday, August 14, 2008 11:57 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] Unidata to Universe port Eugene, I'm sure others will have a longer list, but for starters: 1.The structure of dictionary items is completely different. 2.You lose the ability to expand the print job numbers beyond before they restart numbering print jobs at 1 in UniVerse. Best wishes, 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: Eugene St. Clair [EMAIL PROTECTED] To: u2-users@listserver.u2ug.org Sent: Thursday, August 14, 2008 6:41 PM Subject: [U2] Unidata to Universe port Hello: Does any one have any experiences they would be willing to share regarding the effort required to port applications from UniData to Universe? 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/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Unidata to Universe port
The insert works in Universe provided VAL is not a null string. Subject: RE: [U2] Unidata to Universe port Date: Fri, 15 Aug 2008 11:27:07 -0500 From: [EMAIL PROTECTED] To: u2-users@listserver.u2ug.org Just realized I typo'd make that VAL1 = :@VM:VAL1. Sorry! -Original Message- From: Brenda Price [mailto:[EMAIL PROTECTED] Sent: Friday, August 15, 2008 10:07 AM To: u2-users@listserver.u2ug.org Subject: RE: [U2] Unidata to Universe port When I started working with UniVerse 7 years ago, the main gotcha I ran into was this. INS '' BEFORE VAL1,POS At that time, this worked on all the UniData systems I'd previously worked on but does not work here on UniVerse. We do this to get around it. VAL1,1 = :@VM:VAL1 I am assuming that this occurs on all UniVerse systems but may just be a parameter setup here. I am also assuming that it still works on UniData. Brenda Price --- 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/ _ Get thousands of games on your PC, your mobile phone, and the web with Windows.. http://clk.atdmt.com/MRT/go/108588800/direct/01/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] Unidata to Universe port
Thanks Brenda. I understood what you meant. - Original Message From: Brenda Price [EMAIL PROTECTED] To: u2-users@listserver.u2ug.org Sent: Friday, August 15, 2008 11:27:07 AM Subject: RE: [U2] Unidata to Universe port Just realized I typo'd make that VAL1 = :@VM:VAL1. Sorry! -Original Message- From: Brenda Price [mailto:[EMAIL PROTECTED] Sent: Friday, August 15, 2008 10:07 AM To: u2-users@listserver.u2ug.org Subject: RE: [U2] Unidata to Universe port When I started working with UniVerse 7 years ago, the main gotcha I ran into was this. INS '' BEFORE VAL1,POS At that time, this worked on all the UniData systems I'd previously worked on but does not work here on UniVerse. We do this to get around it. VAL1,1 = :@VM:VAL1 I am assuming that this occurs on all UniVerse systems but may just be a parameter setup here. I am also assuming that it still works on UniData. Brenda Price --- 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/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
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 . 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 = , it will look like this: ED DICT HOLD NEXT.HOLD 2 lines long. : 0001: X Next Available HOLD File Entry No. : 0002: 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 , as illustrated in the following examples: LIST HOLD 04:04:34pm 15 Aug 2008 PAGE1 HOLD... UV^UVNT.SP OOLER^1^N^ 1_ 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 ? 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/
RE: [U2] Unidata to Universe port
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#. 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#_nn,
where
nn is increased for each new print job. If you specify name, the record ID
is
name_nn.
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#_nn,
where
nn is increased by each subsequent SETPTR command. If you specify name, the
record ID is name_nn
...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 .
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 =
,
it will look like this:
ED DICT HOLD NEXT.HOLD
2 lines long.
:
0001: X Next Available HOLD File Entry No.
:
0002:
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 ,
as illustrated in the following examples:
LIST HOLD 04:04:34pm 15 Aug 2008 PAGE1
HOLD...
UV^UVNT.SP
OOLER^1^N^
1_
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 ?
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
Re: [U2] Unidata to Universe port
I didn't realize you were referring to the HOLD file. In that case you are correct about the numbers being only 4 digits. However, you can expand the usage by giving the hold entries names as well as numbers by using the BANNER option. Here is from the manual: BANNER [ name ] 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#. 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#_nn, where nn is increased for each new print job. If you specify name, the record ID is name_nn. BANNER UNIQUE [ name ] In mode 3, append 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#_nn, where nn is increased by each subsequent SETPTR command. If you specify name, the record ID is name_nn. -- From: Dave Taylor [EMAIL PROTECTED] Sent: Friday, August 15, 2008 6:32 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 . 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 = , it will look like this: ED DICT HOLD NEXT.HOLD 2 lines long. : 0001: X Next Available HOLD File Entry No. : 0002: 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 , as illustrated in the following examples: LIST HOLD 04:04:34pm 15 Aug 2008 PAGE1 HOLD... UV^UVNT.SP OOLER^1^N^ 1_ 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 ? 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/
Re: [U2] Unidata to Universe port
Eugene, I'm sure others will have a longer list, but for starters: 1.The structure of dictionary items is completely different. 2.You lose the ability to expand the print job numbers beyond before they restart numbering print jobs at 1 in UniVerse. Best wishes, 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: Eugene St. Clair [EMAIL PROTECTED] To: u2-users@listserver.u2ug.org Sent: Thursday, August 14, 2008 6:41 PM Subject: [U2] Unidata to Universe port Hello: Does any one have any experiences they would be willing to share regarding the effort required to port applications from UniData to Universe? snip --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
