h Time : ':OCONV(TIME(),'MTHS')
CC=40-(INT(LEN(SMSG)/2))
CRT L(17):C(CC):SMSG:EOL
CRT L(20):C(1):
RETURN
*
==
Allen E. Elwood
www.tortillafc.com
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED
Thank you all. It is working now with the VOC pointer. It is much
simpler now that I don't care what account I'm in.
One final question.
I have downloaded many of the pdfs ( UniBasic command ref., Using
unidata, SB+ Solutions, ...) from the IBM site but where is this
documented? Are there any bo
Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Timothy Snyder
Sent: Thursday, 5 January 2006 1:42 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] openseq question
Allen E. Elwood wrote on 01/04/2006 01:29:47 PM:
> I've always found it helpful to open
Allen E. Elwood wrote on 01/04/2006 01:29:47 PM:
> I've always found it helpful to open the file/record in 'regular' mode
first
> to find out if the directory entry worked or possibly to write a null
record
> if it didn't.
So, if the O/S-level file is multi-megabytes, you're reading the whole
Jeff Powell wrote:
> Thanks again to everyone for all their help. I'm almost
there.
>
> I want to use the VOC pointer so I created the pointers in
my Live and
> Test VOC files, logged out and back in to ensure I was
reading VOC but
> I'm still not meeting with any success. When I attempt to
> refe
Jeff, if the VOC entry is MFG.DATA.IPS.TMP then the OPEN is:
OPEN "MFG.DATA.IPS.TMP", MTR.REC TO ...
Not the concatenated thing you had in your post.
-K
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
Thanks again to everyone for all their help. I'm almost there.
I want to use the VOC pointer so I created the pointers in my Live and
Test VOC files, logged out and back in to ensure I was reading VOC but
I'm still not meeting with any success. When I attempt to reference the
pointer I get a "Unin
>Actually I'll need to create two pointers one for the "TEST" account
and another for the "LIVE" account.
This is one of the great features of the VOC pointer; the LIVE account
can point to the directory it needs and the TEST account can point to
the directory it needs and the program doesn't have
Unidata on Unix has this issue, too (at least the DEC Tru64 flavor) -- it holds
onto the file lock after CLOSESEQ of a file OPENSEQed with the Unix path.
Don't know if it's been fixed in newer UD releases, but not likely a priority
since OPENSEQ of a VOC pointer doesn't have the problem.
>>> [E
Jeff;
I use a VOC pointer for exactly this reason. It doesn't matter which
account/where the directory is - I just need the VOC pointer that points
to it. It makes it really easy to transfer from TEST to LIVE.
Also, as Tim pointed out, you don't need the file to exist to open it.
In fact, I have
>Do you recall which OS this was on? I don't believe I've run into
this problem but I'm currently using Windows (2000 and 2003) but I've
also been on RS6000 and DG/UX. All of this is with UV.
Unidata on Windows, as I recall.
-Kevin
[EMAIL PROTECTED]
http://www.PrecisOnline.com
---
u2-users
Thank you for all your helpful suggestions.
I am now looking at creating a VOC pointer as Kevin suggests below.
Actually I'll need to create two pointers one for the "TEST" account and
another for the "LIVE" account.
I had originally tried the PATH:FILE syntax before I found out that the
file nee
lto:[EMAIL PROTECTED] On Behalf Of Kevin King
Sent: Wednesday, January 04, 2006 9:36 AM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] openseq question
I've actually had problems with various versions of Unidata and
CLOSESEQ releasing the file when opening a full path. Opening under a
I've always found it helpful to open the file/record in 'regular' mode first
to find out if the directory entry worked or possibly to write a null record
if it didn't.
I like to have a graph display, and this way I can tell how many 'records'
(or AMCs in this case) I'm going to be processing so I
Several years ago I created a little utility to open sequential files as
needed. It's pretty robust; hasn't given me much trouble over the years.
Like Kevin, I've had problems with the full path version of openseq, so my
utility converts full path mode to VOC pointer mode and creates the VOC
pointe
I've actually had problems with various versions of Unidata and
CLOSESEQ releasing the file when opening a full path. Opening under a
VOC DIR-pointer has never exhibited that problem, so I'd recommend the
VOC pointer approach over using a full path.
-Kevin
[EMAIL PROTECTED]
http://www.PrecisOnlin
I agree with previous posters about using either a full path or creating a
VOC entry that resolves to /tmp.
Although it has nothing to do with the original question, I'd like to make
another observation about the supplied code. In the ELSE clause of the
OPEN, rather than doing a touch of the f
You need to have MTR.FILE.PATH open as a file handle, first. You can do
one of the following:
MTR.FILE.PATH='/tmp'
OPEN MTR.FILE.PATH TO MTR.FILE ELSE STOP
MTR.REC = 'RECID'
OPENSEQ MTR.FILE,MTR.REC TO F.MTR.ROW.FILE ELSE
[what you already have]
END
Or open the full path directly:
MTR.FILE.PA
Your syntax is a little off. When you use the seq.file.name, record.id
syntax then seq.file.name has to be a dir type file. You will have to
either create a voc entry for /tmp, eg.:
TMP.DIR
001 DIR
002 /tmp
003 D_VOC
And then you should be able to: MTR.FILE.PATH = TMP.DIR
Or you can OPENSEQ MTR.
No. /tmp is an absolute path.
On Wed, 2006-01-04 at 09:47 -0500, Koser, Mike wrote:
> Jeff
> Is '/tmp' in the VOC?
> Mike
>
>
> -Original Message-
> From: Jeff Powell [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, January 04, 2006 9:31 AM
> To: u2 users group
> Subject: [U2] openseq ques
Jeff,
I think Openseq looks either for a fully specified path to the file as in :
OPENSEQ "/tmp/recordname" TO F.MTR.ROW ELSE
or it understands the filename, recordname construct but looks for the
filename in the VOC, as in
OPENSEQ TMPFIL, recordname to F.MTR.ROW ELSE...
where TMPFIL is a DI
The syntax is either
OPENSEQ seq.filename,record.id
or
OPENSEQ absolutepath
looks like you are doing a combination. Change it to
OPENSEQ MTR.FILE.PATH:'/':MTR.REC TO F.MTR.ROW.FILE ELSE
Bruce M Neylon
Health Care Management Group
Jeff Powell <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTE
Is it a permissions problem?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Jeff Powell
Sent: Wednesday, January 04, 2006 8:31 AM
To: u2 users group
Subject: [U2] openseq question
Happy New Year.
I am having trouble with the openseq function in UniData. W
Jeff,
AFAIR OpenSeq on UniData looks for either a path name, or if you specify an
item id it looks for an item in a directory file (not a path).
So you would need to either
A) OPENSEQ "/tmp/" : MTR.REC TO F.MTR.ROW.FILE ...
Or
B) create a file pointer to /tmp (e.g. named TMP) and then
OPENS
Jeff
Is '/tmp' in the VOC?
Mike
-Original Message-
From: Jeff Powell [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 04, 2006 9:31 AM
To: u2 users group
Subject: [U2] openseq question
Happy New Year.
I am having trouble with the openseq function in UniData. We are
operation in Pick
25 matches
Mail list logo