Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

Migrating Dec TPU section command file

 
SOLVED
Go to solution
Yyrkoon
Advisor

Migrating Dec TPU section command file

I'm porting from VAX 6.2 to Itanium 8.3


I've a command file which is used to create a tpu section.


I use this command to create the section:


EDIT/NOSECTION/COMMAND=COMMENT.TXT/NODISPLAY/OUTPUT=COMMENT.TPU
$SECTION


and this one to use it


edit/TPU/NOCOMM/SECTION=COMMENT.TPU$SECTION sys$login:test.txt


This works without any issue on the VAX. If I take my comment.txt ftp
it to the Integrity Itanium box I can create the section file with
success. But when I try to edit the file I got a DEC TPU error.


Shareable base: 7B778884 Ident: DECTPU V3.2 2007-08-30 10:53
Updater base: 7BA4C034 Ident: DECTPU V3.2 2007-08-30 10:53
Updater file:


%NONAME-F-NOMSG, Message number 00000004
-TPU-F-BADSTATUS, return status 7BAA5058 different from last signal
00000000
-SYSTEM-?-EXQUOTA, process quota exceeded
-RMS-?-BADESCAPE, syntax error in escape sequence
Message number 0002FFFF
Normal successful completion
-TPU-F-BADSTATUS, return status 7BAA5058 different from last signal
00000000
-SYSTEM-?-EXQUOTA, process quota exceeded
-RMS-?-BADESCAPE, syntax error in escape sequence
Message number 0002FFFF
Normal successful completion


I guess that some of the commands on the command file is not valid
yet, but I do not know how identify or debug it. Someone could light
my way?


7 REPLIES 7
Steven Schweda
Honored Contributor

Re: Migrating Dec TPU section command file

> -SYSTEM-?-EXQUOTA, process quota exceeded

I'd start with:

show process /quota

on both systems. You should expect to need
more memory on IA64 than on VAX.
Hoff
Honored Contributor
Solution

Re: Migrating Dec TPU section command file

Whether this is a TPU bug or a bug in the TPU code is not known.

Given you likely have access to a support contract, ring up HP and ask. They'll want to see the source code for the section, too.

The error messages are clearly corrupted, which implies that the entire stack is suspect. Though (as mentioned) you might try increasing the quota, on the off chance that error is actually valid; that ? implies it might not be.

I'd expect to need around 5x for the memory-related process quotas for OpenVMS I64 as was typically found on OpenVMS VAX, though that is a general estimate (guess) and requirements can vary from that. Widely.

Personally, I'd expunge the TPU code. Old VAX code using an old and ill-maintained language? If it's not particularly involved, replace it. It's one less maintenance problem to have around. Any recent scripting language (lua, php, python, perl and sometimes even DCL) can often be an effective replacement for much of what I've seen with TPU used for over the years, and custom tools built from flex/bison or lex/yacc or tparse can often be pressed into service for the rest of what TPU gets used for.

And FWIW, this question is cross-posted to:

http://groups.google.com/group/comp.os.vms/browse_thread/thread/bc7077556010f573
Hein van den Heuvel
Honored Contributor

Re: Migrating Dec TPU section command file


How was your account on the Itanium created?
Cloned from the VAX?
Cloned from a reasonably configured default?

Check out the basics like BYTLM (100000), FILLM (500), PGFLQUO (100000),...

You can try running with SHOW PROC/CONT in an other window selecting the 'q' (for Quota) srceen and see if you can spot the low quota.
Maybe try without the section first.

Hein
John Gillings
Honored Contributor

Re: Migrating Dec TPU section command file

Yyrkoon,

If it's not too big, perhaps you could post the TPU source code?
A crucible of informative mistakes
Yyrkoon
Advisor

Re: Migrating Dec TPU section command file

Many thanks all, but it is a legacy application and we cannot change anything, on the other hand 1.200 lines is to much to post here, I will look for another solution myself and I let you know if I find it.
Robert_Boyd
Respected Contributor

Re: Migrating Dec TPU section command file

If it's a 1200 line TPU script there's a very good chance that you will be bumping up against process quota differences between VAX and Integrity.

I have some pretty hefty TPU stuff that I ported to Alpha and ran into similar issues back then.
Master you were right about 1 thing -- the negotiations were SHORT!
John Gillings
Honored Contributor

Re: Migrating Dec TPU section command file

>but it is a legacy application and we cannot change anything

Huh? Other than jumping from VAX, over Alpha to Itanium, a radically different architecture, close to 20 years of hardware differences, and 7 (8?) operating system versions?

And you don't expect to have to change ANY software, even in the face of very obvious compatability issues?

me thinks someone has some slightly unrealistic expectations...

;-)
A crucible of informative mistakes