I am attempting to parse out the original pathname of a cataloged program
from the object code. I am looking for some guidance on how to interpret the
symbol table at the end of the file. Prior to the Basic compiler release
6.2.2 it appears that the pathname could be stripped off the very end of
I may have posted too soon. With a little more searching I found Gyle
Iversons SRS.UV.HEADER program. It looks like it will do the trick.
Vance
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Vance Dailey
Sent: Thursday, March 11, 2004 1:55 PM
To: U2-Users
I looks like a great product, but since its a windows application it will
not meet our needs. Thanks for the tip.
Vance
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Hennessey, Mark F.
Sent: Friday, March 05, 2004 8:43 AM
To: U2 Users Discussion List
The price is right. I'll have to do some testing to see if changing from
wyse 60 is going to be a headache. Thanks for the suggestion.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Cameron Booth
Sent: Thursday, March 04, 2004 6:25 PM
To: U2 Users
I had not considered such a minimal solution. I will have to see if our
application can run under a VT emulation. What are the limitations of
running Universe applications without a separate terminal emulator?
Thanks,
Vance
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL
Is there any way to directly access information stored in the file header? I
use the information returned by the FILE.USAGE command to determine if a
static file can be archived or if it needs to be checked to see if it needs
to be resized.
Vance
-Original Message-
From: [EMAIL
Cool. I found the include file with the following comment:
* 04/23/99 24742 GMH Add special FINFO$HDRLAYOUT and access keywords ;-)
But my include file only includes keys up to the following line:
EQUATE FH$RESIZEPATH TO 95
I am running 9.6. Were the extra keys added in a later release
from my experience.
I want to thank everyone who offered help and took the time to make
suggestions.
Vance Dailey
-Original Message-
From: Vance Dailey [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 03, 2004 5:23 PM
To: '[EMAIL PROTECTED]'
Subject:UV command
changes fixed the problem. If the problem is solved I will
post in case someone else runs in the same problem in the future.
Thanks,
Vance Dailey
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Ken Wallis
Sent: Sunday, February 08, 2004 7:52 PM
To: 'U2 Users
know
what I find. Thanks for the tip.
Vance Dailey
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Dave Kimmel
Sent: Wednesday, February 04, 2004 11:08 PM
To: U2 Users Discussion List
Subject: Re: UV command failing mystery
On Feb 4, 2004, at 4:38 PM, Vance
executed by a terminal users and a phantom. Perhaps the command fails in the
process of checking the licenses?
Thanks,
vance Dailey
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Hennessey, Mark F.
Sent: Friday, February 06, 2004 11:51 AM
To: U2 Users Discussion
It looks like the command is dg_strace for DG/UX. My problem is that I
don't understand the output yet. It looks like it may be a good tool to know
how to use.
Thanks,
Vance Dailey
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Gerry Maddock
Sent: Friday
executed by a terminal users and a phantom. Perhaps the command fails in the
process of checking the licenses?
Thanks,
vance Dailey
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Timothy Snyder
Sent: Friday, February 06, 2004 11:55 AM
To: U2 Users Discussion
It was suggested that I try to run dg_strace. I ran it on one of the failing
uv processes. It generated a 1mb file. I can see where it executes uvsh
and It fails just after the 7th occurance of RUN APP.PROGS PACKAGE.INS.
(The 7th run is just after the string SPECIAL.EDITOR.SELECT.DATA\OLONG.) I
no problems and no unusual locks we noted when we used the
command list.readu every. analyze.shm -s does not show any unusually
high numbers of Collisions. Are there any log files we should be checking?
We are more puzzled than ever.
Vance Dailey
-Original Message-
From: [EMAIL PROTECTED
101 TO 50
GSEMNUM 211 TO 97
GLTABSZ 150 TO 75
RLTABSZ 150 TO 75
MAXRLOCK 100 TO 74
Any help solving this puzzle would be greatly appreciated.
Thanks,
Vance Dailey
--
u2-users mailing list
[EMAIL PROTECTED]
http://www.oliver.com/mailman/listinfo/u2-users
16 matches
Mail list logo
