Does that syntax work on your UniData?!? I just barfs up trying that
syntax
on mine. If it does work, let me know your version.
I get a syntax error also. Sorry I use that in Unibasic and thought it
might work for this too.
Charles Shaffer
Senior Analyst
NTN-Bower Corporation
On 11/3/2010 1:26 AM, David Wolverton wrote:
Yes -- this does work --
It also turns out it DOES work using the 'tab' key, but looks bad, but that
it will not work from an SB+ '/TCL shell'.
I'm sort of hoping the new features (which includes a 'database viewer' I
hear) will make this kind of
Although I have been globally cataloging subs for some time, is there any point
in cataloging standard application programs?
Of course, end-users are able to launch the compiled application programs via
VOC.
Suggestions would be appreciated.
--Bill
the biggest I can think of, is that it allows you to compile a programs
changes and test them, without interferring with production (if they
are running the cataloged program), once it's ok - then recatalog to
put into the production usage.
-Original Message-
From:
What I have been doing is creating a new revision to PART.MGR.R101.
Called PART.MGR.R102
Thus when PART.MGR.R102 has been tested in the SandBox, VOC in our live system
is updated from ...101
Standard application programs ?
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Bill Brutzman
Sent: 03 November 2010 18:53
To: U2 Users List
Subject: [U2] Cataloging Programs
Although I have been globally cataloging subs for some time,
Standard meaning... vanilla green-screen.
--Bill
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Symeon Breen
Sent: Wednesday, November 03, 2010 4:10 PM
To: 'U2 Users List'
Subject: Re: [U2] Cataloging Programs
On earlier versions of SB+ - running on Unidata - we have created a couple
of processes that can be used to create and delete a temporary work file for
use by whatever logic falls between the CREATE.WORK.FILE and
DELETE.WORK.FILE processes. In trying to port these to SB/XA on UV we're
running
If we're talking Unidata there are memory considerations based on how
something is cataloged. Catalog something globally and throw a thousand
users at it and at most it'll be loaded into memory once. Don't catalog it,
or catalog it locally or direct and each user will get their own copy of the
Found the issue. Apparently in this version of SB+ when you WRITE something
to a file in a paragraph, SB+ opens the file to a buffer variable that it
holds open until the paragraph terminates. So when the paragraph (with the
WRITE) called the DELETE.WORK.FILE routine, the calling paragraph had
10 matches
Mail list logo
