<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:Garamond;
        panose-1:2 2 4 4 3 3 1 1 8 3;}
@font-face
        {font-family:"Arial Rounded MT Bold";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p
        {mso-style-priority:99;
        mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";}
span.EmailStyle20
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
span.EmailStyle21
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle22
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
span.EmailStyle23
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle24
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle25
        {mso-style-type:personal;
        font-family:"Garamond","serif";
        color:blue;
        font-weight:normal;
        font-style:normal;}
span.EmailStyle26
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='color:#1F497D'>Wow, we migrated to Itanium several years ago and noticed no sort issues. We were on RMS files though, and it seems to be a common thread that Rdb users are having more problems.<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> powerh-l-bounces+rwitkopp=phxa.com@lists.sowder.com [mailto:powerh-l-bounces+rwitkopp=phxa.com@lists.sowder.com] <b>On Behalf Of </b>Lorry Litman<br><b>Sent:</b> Monday, August 24, 2015 1:20 PM<br><b>To:</b> 'Thomson, Martyn'; 'HERALD KAFFKA'; 'powerh-l@lists.sowder.com'<br><b>Subject:</b> RE: Alpha to Itanium DCL issue<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-CA style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'>Martyn, that’s great you were able to isolate the RDB error.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'>I wasn’t aware of the sort issue Herald mentioned but certainly something I’ll make note of.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'>The following I add in case someone is running older software/hardware and has experienced some oddities.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'>We are running VMS 7.3-2 and PH 7.10.E6 & 7.10.G1 and Oracle RDB 7.0-1 on Alpha ES47 machines.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'>This past year when we upgraded VMS from 7.3-1 to 7.3-2, minimum version for HP support, and for our disk storage upgrade and changed machines from GS160 to ES47 I ran into some odd behaviour.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'>A command procedure would be executing code, whether QTP or RDB SQL and the command procedure would just terminate. No error message, nothing in the log file.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'>This same process termination would also happen to user processes that were logged into and accessing application screens.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'>The other situation encountered is that sometimes QTP code (or RDB SQL) would execute but the process would hang. No CPU cycles or I/O, nothing, just hung.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'>we couldn’t contact Unicom/Cognos or RDB for support because we are running unsupported versions (no support contract).<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'>To try to isolate this I created a command procedure that simply ran one QTP program that read a couple RMS files and updated some information in an RDB table. Following this it would run a QUIZ program. The QTP program would always run and complete but the command procedure/process (interactive or batch) would terminate right after. No other code not even next line being show $status executed.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'>Using the accounting utility one thing I found is that the processes, interactive or batch, had a final status of %SYSTEM-F-ASTFLT.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'>I contacted HP to try to help analyze what might be going on. Using Analyze/sys, a variety of information was gathered for processes that terminated and the processes that were hung.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'>Other errors were identified such as<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'>-RMS-F-SYS, QIO system service request failed<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'>-SYSTEM-F-EXQUOTA, process quota exceeded<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'>Note: If your command procedure is run in batch or /out=logfile and there is nothing at the end of the logfile. Do $set file/end and then type the file to see if there is anything of interest.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'>For specific accounts we increased quotas for TQELM, ASTLM, and ENQLM. For some situations this seemed to help but sporadically.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'>One of the things HP noticed but had no explanation is that some code was being executed in executive mode on the stack when it shouldn’t be and thus would not be able to return resulting in hung or terminating process.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'>No definitive answer or solution yet. A bunch of work arounds and monitoring procedures were put in place to deal with the situations. Fortunately, many of the applications have been migrating off of this platform so fewer and fewer are affected/impacted.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'>We are in the process of isolating one of the old GS160 and loading all the pre-upgrade software. Then step through the upgrade with HP to see where things may have gone amiss.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'>Part of the reason is because we also found other issues when compiling some of our 30 year old Macro code.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'>Answer to the MACRO code compile problem we found<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'>The $TRAN macros now need to know whether they are being used on Alpha or Itanium (they are common source).<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'>The developer who made the changes added various ".IF DF EVAX" and ".IF DF IA64" directives to the macro. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'>The Alpha version wasn't scheduled to be changed until 8.2, but the common source accidently slipped into V7.3-2.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'>Those symbols are not part of the Macro-32 compiler itself, but come from a file called SYS$LIBRARY:ARCH_DEFS.MAR.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'>So add /MIGATE to your MACRO command and add SYS$LIBRARY:ARCH_DEFS.MAR with the file your compiling.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'>Thanx</span><span style='font-size:12.0pt;color:blue'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'>Lorry Litman</span><span style='font-size:12.0pt;color:blue'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'>Application Management</span><span style='font-size:12.0pt;color:blue'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'><a href="mailto:llitman@manitoba-ehealth.ca">llitman@manitoba-ehealth.ca</a></span><span style='font-size:12.0pt;color:blue'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'>204-926-9076</span><span lang=EN-CA style='color:blue'><o:p></o:p></span></p></div><p class=MsoNormal><span lang=EN-CA style='font-size:12.0pt;font-family:"Garamond","serif";color:blue'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> <a href="mailto:powerh-l-bounces+llitman=manitoba-ehealth.ca@lists.sowder.com">powerh-l-bounces+llitman=manitoba-ehealth.ca@lists.sowder.com</a> [<a href="mailto:powerh-l-bounces+llitman=manitoba-ehealth.ca@lists.sowder.com">mailto:powerh-l-bounces+llitman=manitoba-ehealth.ca@lists.sowder.com</a>] <b>On Behalf Of </b>Thomson, Martyn<br><b>Sent:</b> Monday, August 24, 2015 2:05 PM<br><b>To:</b> 'HERALD KAFFKA'; 'powerh-l@lists.sowder.com'<br><b>Subject:</b> RE: Alpha to Itanium DCL issue<o:p></o:p></span></p></div></div><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'>Thank-you for your suggestion!<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'>I was looking for a Powerhouse *<b>E</b>* type error message. Turns out it was an <b>%RDB-E-</b> error on a date conversion in a view.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'>Because the dozen QTP programs were being executed in the same QTP session, it just carries on regardless executing the others, then aborts when it exits back to DCL. Who knew!<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'>I’ll split them up into separate “$ QTP auto=” statements so DCL will error out on the right one.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'>Thanks again Herald.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Thomson, Martyn <br><b>Sent:</b> August-24-15 11:21 AM<br><b>To:</b> 'HERALD KAFFKA'; 'powerh-l@lists.sowder.com'<br><b>Subject:</b> RE: Alpha to Itanium DCL issue<o:p></o:p></span></p></div></div><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'>“com” is just a logical for the location of DCL command procedures. Used throughout the app.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'>I’ll try your suggestion of running each procedure from command line.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> HERALD KAFFKA [<a href="mailto:Herald.Kaffka@westfraser.com">mailto:Herald.Kaffka@westfraser.com</a>] <br><b>Sent:</b> August-24-15 11:07 AM<br><b>To:</b> Thomson, Martyn; 'powerh-l@lists.sowder.com'<br><b>Subject:</b> RE: Alpha to Itanium DCL issue<o:p></o:p></span></p></div></div><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>RDB? Oracle? Or straight RMS/ISAM…<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>About 2 years ago we went through the same process (Large Powerhouse application => Alpha->Itanium).<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>App was a mix of Oracle and RMS/ISAM (mostly Oracle with a few legacy RMS files hanging around…). (No RDB).<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Near Zero problems with the OS/Shell. (Alpha by default ran a stable sort, Itanium ran a unstable sort, so if <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Your quiz/qtp runs were sorting down x levels, and detail lines were at x+1, the order of the detail lines was <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Undetermined. (Subtotals were ok, ie Sort down to the level of a “parent company”, (say Home Depot), then<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Display sales to each individual store, subtotals/grand totals would all be good, but the order in which individual<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>Stores printed out was random, (oracle returns data in a random order if you don’t explicitly sort, if you are using pure<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>RMS/ISAM you would be fine as RMS runs indexes and retrieves in order). “I think” there was a logical you could set<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>To force the old behavior, but as this only affected about 4 quiz/qtp runs out of hundreds, we simply added the last sort <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>level to reports. (Cleaner and easier to understand in the long run than using an invisible logical name out at the system level…).<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>This was pretty much the only problem we ran into on this. (course we had moved from various VAXes in the past, and from <o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'>VAX to Alpha, so there is/was a pretty good abstraction layer setup in logical names to hide the physical hardware…).<o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA>“@com:proc2.com”;<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA>Is the @com in the above an “inhouse” symbol/procedure to run a command file? You might want to look at it if so, and see if it’s your problem…<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA>If your routine is not too involved, you might want to step through processing one step at a time at the DCL command line to see if something <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA>Is getting trapped out (and/or confused) by something in the com file wrapper/driver…<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA>Just a few random thoughts… </span><span style='color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> <a href="mailto:powerh-l-bounces+herald.kaffka=westfraser.com@lists.sowder.com">powerh-l-bounces+herald.kaffka=westfraser.com@lists.sowder.com</a> [<a href="mailto:powerh-l-bounces+herald.kaffka=westfraser.com@lists.sowder.com">mailto:powerh-l-bounces+herald.kaffka=westfraser.com@lists.sowder.com</a>] <b>On Behalf Of </b>Thomson, Martyn<br><b>Sent:</b> Monday, August 24, 2015 12:03 PM<br><b>To:</b> 'powerh-l@lists.sowder.com' <<a href="mailto:powerh-l@lists.sowder.com">powerh-l@lists.sowder.com</a>><br><b>Subject:</b> Alpha to Itanium DCL issue<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-CA>Moving a large PowerHouse app from Alpha to Itanium. Getting strange behaviour with a DCL procedure terminating prematurely.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA>DCL procedure proc1.com submitted;<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA>Does a few things then executes proc2.com i.e. “@com:proc2.com”;<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA>Proc2.com runs a dozen QTP programs then drops out to proc1.com prematurely! The QUIZ programs don’t get run; the reports aren’t printed;<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA>On returning to proc1.com it immediately exits, not executing the remainder of proc1.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA>All QTP/QUIZ were recompiled.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA>I added “on error then goto err_handler” to both procedures to display $status. Proc2 is terminating with %X1900802A. That’s a QTP error “A file access error has been detected, but the QTP program did write to the database the number of records shown in the log. The protection on all tables it references is correct. There are no subfiles involved.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA>Has anyone seen this before? Very puzzled. Any insights, suggestions, etc much appreciated.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA>I should point out I searched the logs on the Alpha for this job. It happened once last month for the first time ever.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA>OpenVMS 8.4<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA>Oracle Rdb SQL V7.3-100<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA>PowerHouse 8.40G<o:p></o:p></span></p><p class=MsoNormal style='margin-top:6.0pt'><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>Regards, <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='font-family:"Arial Rounded MT Bold";color:#1F497D'>Martyn Thomson<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='font-family:"Arial","sans-serif";color:#1F497D'>Senior Technical Analyst, Development Services</span><span lang=EN-CA style='font-family:"Arial Rounded MT Bold";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA style='font-family:"Arial","sans-serif";color:#1F497D'>Information Technology Services<o:p></o:p></span></p><p class=MsoNormal><b><i><span style='font-size:14.0pt;color:#003D83'>HP Advanced Solutions Inc.<o:p></o:p></span></i></b></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>phone: 250.405.4555 | fax: 250.405.4422</span><span lang=EN-CA style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>email:<a href="mailto:martyn.thomson@hpadvancedsolutions.com">martyn.thomson@hpadvancedsolutions.com</a> </span><span lang=EN-CA style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D'>web: <a href="http://www.hpadvancedsolutions.com/">www.hpadvancedsolutions.com</a> <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-CA><o:p> </o:p></span></p><p><br><br>-------------EOP--------------- <br><br>This e-mail message and any attachments are confidential. Any dissemination or use of this information by a person other than the intended recipient is unauthorized. If you are not the intended recipient, please notify me by return e-mail, do not open any attachment and delete this communication and any copy. <br><br>Thank you <o:p></o:p></p></div>
<P>securemail.phxa.com made the following annotations<br/>---------------------------------------------------------------------<br/><br>NOTICE: The information contained in this e-mail and <br>any attachments is confidential and may be privileged <br>or otherwise protected from disclosure.This e-mail is <br>intended solely for the use of the named addressee. <br>Any other use, printing, copying, disclosure or <br>dissemination may be subject to legal restriction. If <br>you are not the intended recipient, please contact the <br>sender and delete all copies including any attachments.<br>
<br/>---------------------------------------------------------------------<br/>
</P></body></html>