RE: [U2] Unidata to Universe port

2008-08-15 Thread Symeon Breen
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

2008-08-15 Thread George Land
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

2008-08-15 Thread jpb-u2ug
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

2008-08-15 Thread Brenda Price
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

2008-08-15 Thread Brenda Price
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] Uniobjects for Java

2008-08-15 Thread Charles_Shaffer
Hello,

I am accessing our Unidata server from PHP using the java bridge for a few 
months  It has been working pretty well up until the current project I am 
working on.

PHP calls a method in a U2 object, which uses Uniobjects for Java to 
invoke a UniBasic Subroutine on our Unidata 7.1 redhat based server. 
Recently I have intermittently received the following error message. 
**
Fatal error: Uncaught [[o:Exception]:java.lang.Exception: Invoke failed: 
[[o:U2]]-PbrGetMgrList. 
Cause: java.lang.NoSuchMethodException: PbrGetMgrList(). 
Candidates: 
[] Responsible VM: [EMAIL PROTECTED]://java.sun.com/ at: 
#-5 php.java.bridge.JavaBridge.Invoke(JavaBridge.java:1045) 
#-4 php.java.bridge.Request.handleRequest(Request.java:405) 
#-3 php.java.bridge.Request.handleRequests(Request.java:481) 
#0 java.inc(257): java_ThrowExceptionProxyFactory-getProxy(52, '@N', 
true) 
#1 java.inc(473): java_Arg-getResult(true) 
#2 java.inc(479): java_Client-getWrappedResult(true) 
#3 java.inc(672): java_Client-getResult() 
#4 java.inc(1786): java_Client-invokeMethod(51, 'PbrGetMgrList', Array) 
#5 java.inc(1910): java_JavaProxy-__call('PbrGetMgrList', Array) 
#6 java.inc(2072): java_AbstractJava-__call('PbrGetMgrList', Array) 
#7 [internal function]: Java-__call('PbrGetMgrList', Array) 
#8 /var/www/pbr/pbr.php(14): Java-PbrGetMgrList() 
#9 {main}] thrown in java.inc on line 220

I am not sure what this is referring to.  I don't find a java.inc anywhere 
on the web server host.

This works most of the time, but sometimes not.  and I don't see a 
pattern.  Most of the time it can be fixed by recompiling and rejarring 
the Java object, but that doesn't always fix it.  One thing I wondered 
about is that this is the first time that I have called a program with no 
input parameters.

Here is the java code.

/**
 * @param   none
 * @return  Tab delimited list of MGR_NAMES
 */
public String PbrGetMgrList() {
String result = ;
try {
OpenU2Session();
UniSubroutine uSub = uSession.subroutine(PbrGetMgrList, 
1);
uSub.call();
result = uSub.getArg(0);
CloseU2Session();
} catch (UniSessionException e) {
result = N;
} catch (UniSubroutineException e) {
result = N;
} finally {
return result;
}
}

Here is the UniBassic Subroutine code

$BASICTYPE 'U'
SUBROUTINE PbrGetMgrList(RESULT)

* Tab delimits data items
EQU HTABTO CHAR(9)


* Select records for this supervisor

RESULT = 'N'
ECMD = SELECT MGRACCT.DATA SAVING UNIQUE NAME
EXECUTE ECMD
IF @SYSTEM.RETURN.CODE = 0 THEN RETURN
 
***
*  Build the list
***
RESULT = ''
FIRST = 1
LOOP
READNEXT ID ELSE ID = ''
UNTIL ID = ''
* Insert a delimiter unless this is the first record
IF FIRST = 0 THEN
RESULT := HTAB
END ELSE
FIRST = 0
END
* ADD THE ID
RESULT := ID
REPEAT
RETURN

I suspect that an exception is happening that is not being handled.  Any 
ideas?
 
Senior Analyst
NTN-Bower Corporation
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


Re: [U2] Unidata to Universe port

2008-08-15 Thread Eugene St. Clair
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

2008-08-15 Thread Ron Hutchings
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

2008-08-15 Thread Eugene St. Clair
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

2008-08-15 Thread Dave Taylor

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] [UV] Editing Paired Value Marks - Victory

2008-08-15 Thread MAJ Programming
I'm surprised at the attention this thread caused.

Could the following have worked on UV or UD. Works everywhere else.

SELECT FILE WITH F1 = '[]'

where single quotes bound the double quote bounded by square brackets.

This has worked since day #1 over 30 years ago.

My [1] cent
Mark Johnson
- Original Message - 
From: Brutzman, Bill [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Wednesday, August 13, 2008 2:04 PM
Subject: RE: [U2] [UV] Editing Paired Value Marks - Victory


 Thanks to those who responded.
 
 Using AE I was able to do a...
 
 1: C/Sales.Order.ID^253/Sales.Order.ID
 
 --Bill
 ---
 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] [UV] Editing Paired Value Marks - Victory

2008-08-15 Thread MAJ Programming
shameless ad for Accuterm
Accuterm's WED shows 253's and 252's as regular editable characters.
/ad

Plus all non UV/UD original Pick EDitors allow Shift-] or Shift-\ or
Ctrl-shift-^ for 253, 252 and 254 respectively.

Again, since day #1.

My [1] cent
Mark Johnson
- Original Message -
From: Brutzman, Bill [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Wednesday, August 13, 2008 2:04 PM
Subject: RE: [U2] [UV] Editing Paired Value Marks - Victory


 Thanks to those who responded.

 Using AE I was able to do a...

 1: C/Sales.Order.ID^253/Sales.Order.ID

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

2008-08-15 Thread Bill Haskett
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

2008-08-15 Thread JPB-U2UG
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/