7.29C8 and 8.19
georgia miller
georgia_miller@gfps.k12.mt.us
16 Mar 1999 12:16:33 -0700
I am currently converting all my systems on our HP3000 from PH729.C3 to PH819.C3. These are the Issues That I identified from this list and other sources.
Problems to Watch out for in Powerhouse Vs 8.19.C
1. Subfiles
A. If Quiz or Qtp attempts to purge a nodictionary subfile, it will hang - forever. The solutions are to purge the nodictionary subfiles prior to re-writing them...or just have no nodictionary subfiles (I believe in the latter).
Ron Tilby - Raytheon Aircraft Montek Co.
The QTP Parser hangs when processing a SUBFILE xxx KEEP
NODICTIONARY command if the permanent subfile already exists.
Example:
:comment Initially build the subfile
:PURGE XXX
:QTP
>ACCESS EMPLOYEES
>SUBFILE XXX KEEP NODICTIONARY INCLUDE EMPLOYEES
>GO
>EXIT
:comment Now that the subfile exists, we can exhibit the problem.
:QTP
>ACCESS EMPLOYEES
>SUBFILE XXX KEEP NODICTIONARY INCLUDE EMPLOYEES
:comment the system never returns a '>' to continue input.
:comment in batch, the job will just sit there.
This problem prevents compiling QTP runs that create or append to permanent nodictionary subfiles. I've produced this problem using Image Detail Datasets and Native Mode KSAM files as the input file. It occurs whether or not the input record length is an even or odd number. I have NOT seen this problem in 7.09 or 7.29.C8, it appears to be new in 8.19
Workaround from Bob Deskin - Senior Product Advisor - Cognos Inc.
Certainly the parser should not hang. As a possible workaround, have you
tried specifying the old subfile's format? Or try the SUBFORMAT program
parameter. 8.19 uses a new subfile format and that could be hanging
things up.
B. Subfiles are now format 8...so if you want to write to a format 7 subfile (or an even earlier version), the process will error.
From: Exequiel R. Sevilla III (aka Kelly) <ersevilla@west.raytheon.com>
C. When upgrading from 729 to 819 you will get some subfile format 7 error messages. To resolve this you must purge the subfiles and rebuild in 819C.
From: Michael Lee <mclsys@home.com>
2. OMNIDEX
My problem is that I found out that PH8.19C1 does not work with an older version
of Omnidex (3.4.11). I'm also upgrading THAT also to 3.4.62B. I've figured out
the following truth so far:
Omni 3.4.11 Omni 3.4.62B
Quiz 7.29C2 Yes ?
Quiz 8.19C1 No Yes
From: Tracy Johnson <tmj@primenet.com>
According to the 8.19.C1 Installation Document the lowest version of Omindex to support PH 8.19 is 3.4.61E.
3. Get Fatal Error 45 (42?) with some programs when compiling in QUIZ. This is fixed in 819C4 (which has not been released yet).
4. ALLBASE
A. If you use the option CLEAR_PENDING_ROLLBACK to alleviate rollbacks in Allbase you actually get more rollbacks in 819C2. I don't believe this has been fixed. ..we are getting more rollback errors in 819C than in 729C7. It turns out it was having the option "CLEAR_PENDING_ROLLBACK" on the QUICK call. When this option was removed from the UDC that called QUICK the problem went away. Since the option was put there for a reason the $64,000 question is... "is the cure worse than the disease?". Only testing will tell, I guess. This has been reported to Cognos CS but a bug number hasn't been assigned as yet. Michael Lee - MCL Systems Inc. 9/11/98
B. According to the Cognos 8.19 Installation Document you must have at least version G2.04 of Allbase/SQL
5. The PDL Dictionary must be recompiled under Version 8.
Simple recompile from 7.29. Users didn't notice any difference.
John Pickering - JWP Systems Inc. - Toronto
6. MB Foster's ODBS Driver
3 problems are listed in the Cognos 8.19.C1 Installation Document
7. KEEP CURSOR in 7.29 application and port to 8.19, you will get a warning about KEEP CURSOR. You can ignore the warning and remove the KEEP CURSOR statement. This will not effect the running of your application. - Cognos 8.19
8. Quiz & QTP Cannot Read Portable Subfiles Containing Datetime Datatypes
When a portable subfile is created in QUIZ or QTP using a datetime datatype,
PowerHouse 4GL 8.19 will not be able to read that portable subfile. -
Cognos 8.19 Installation Document
9. French & German Alternate Message Files are not available in this version.
10. Scrolling Date Fields Redrawn & Displayed
PH 8.19 redraws and displays screens with scrolling fields whenever it encounters
them. This problem is more visible now that the new ALLOW CENTURY option uses
horizontally scrolling date fields to include the century without having to
reformat the field. Examples of the problem are displayed ghost screens and
screens that flash when a return to stop screen command is executed. -
Accordiing to Michael Lee - MCL Systems Inc. this was fixed in vs 8.19C2
although it is not listed as a bug fix on Cognos' Product Updgrade Advisor on the Web.
11. 'EXIT' from PDL terminates job on the HP3000
Any commands after the Exit in a job stream are ignored as the Exit command
terminates the job. The workaround is to add an !EOD stmt after the EXIT in the job stream.
!JOB
!PDL
use pdlsrc
EXIT
!EOD
! >> other commands
!EOJ
Steve Miller <steve@portionpac.com
Ron Tilby <Rtilby@montek.com>
12. addcentury(date_6) convert to addcentury(date_6,century(date_6)
John Pickering <pickerij@norbord.com
13. FR designer procedure not conflicts with the scrolling screen first record action field command.
John Pickering <pickerij@norbord.com
14. Documentation
Only problems discovered so far are no coghelp on the tape, no qkmsgf on the tape
and the manuals are on cd. None is a big deal - missing files promised with the
lawyers' letter and the cd actually isn't too bad.
John Pickering - JWP Systems Inc. - Toronto
15. We are going from PH729c6 to PH819c. These screens work and are currently in
production using ph729c6. We are running in a ghost screen environment to allow
movement from any one screen to any other screen. While running a popup to allow
entry to perform a key change, we are passing a temporary item back to the
calling screen. In the PH819c version, when performing a return from the
popup screen we get the following error:
Code Trap :
01634010227
00122161137
00000000641
00000000017
*E* Memory fault (invalid address).
*Fatal Error* *1504* Notify Cognos Customer Support
hickeyt@gatesmcdonald.com 9/14/98
This is my YR 2000/8.19C3 Upgrade Process For Accounts:
1. Create a new account if a test account does not exist.
a. log on to system manager
b. :NEWACCT x,mgr_name;CAP=same as orig;ACCESS=(same as orig);LOCATTR=3
c. give the New acct manager a password
2. Store the entire account on a dat tape
:RR
/SELECT @.@.ACCOUNT STORE TO TAPE
/GO
3. Restore all the files to the test account
:RR
>Select @.@.origacct restore from tape
>change account origacct to testacct
>change creator @.origacct to @.testacct
>create all
>/go
4. Change SETCOGPH.CMDGFPS.SYS so that the new test account uses PH819C
(we use a powerhouse command file instead of the Cognos UDC's)
5. Purge all PH subfiles with file-code = 644
:MPEX
%listf @.@ (code="644")
%purge @.@ (code="644")
%exit
6. Make all changes to PDLSRC.DICT as needed for Year 2000 issues:
*Change the SYSTEM OPTIONS stmt:
Add ALLOW CENTURY
Add DEFAULT CENTURY 19
Add INPUT CENTURY 19 FROM YEAR 20
Should have CENTURY INCLUDED regardless of whether the majority of
dates are 6 character or 8 character dates. Overide this were ever a 6 digit date is kept.
*May want to add ALLOWCENTURY to USAGE stmts esp. on Birthdates.
USAGE fieldx SIZE n ALLOWCENTURY
7. In the PDLCOMP.DICT job to recompile the PDL dictionary you must add !EOD
after the EXIT stmt in order for any stmts to be read after the EXIT from PDL.
(May already be there)
8. STREAM PDLCOMP.DICT to recompile the PDL dictionary.
9. Create an MPEXPRNT job and stream.
This will identify if there are any issues from 7.29C to 8.19C. Checks for:
"NODICTIONARY", "FILE QKMSG", "CENTURY", "PROCEDURE DESIGNER FR ",
"PHDATE",
10. Make any source changes as identified by #9 or as needed for Yr2000 issues.
Keep a list of all sources changed to move to the production account at a later date.
*Where ever you are dealing with a 6 digit date and you are going to convert it to
an 8 digit date or do a Date function on it, you must convert it to a century included
date with this code: DEFINE datex DATE =
ADDCENTURY(six_digit_date,CENTURY(six_digit_date))
*May want to add ALLOWCENTURY to FIELD or CHOOSE stmts esp. on Birthdates.
*May need to add NULLSEPARATOR to report items on QUIZ in order to print
century on dates and not use more columns of the report.
11. Check your PH compile jobs to be sure all objects will be recompiled.
12. Stream the PH compile job(s) to recompile all PH objects.
13. Convert to OMNIDEX 3.4.63B per the instructions.
14. If any date fields are converted from 6 digit dates to 8 digit dates, you will need to
create a valid Unload, recreate, load database QTP job - now that I have Architect 8.19C use that.
15. Change QEDITMGR.PUB to use PH819UDC.PH819C3.COGNOS instead of 729
16. On January 1, 2000, we will want to change the default century in the dictionaries
to 20 from 19 and recompile.
Georgia Miller, Systems Analyst
Great Falls Public Schools
Email: georgia_miller@gfps.k12.mt.us
____________________________________________________________________
>To: 'powerh-l@lists.swau.edu'
>From: Shah, Roshan (Windsor, HQ) on Tue, Mar 16, 1999 9:08 AM
>Subject: 7.29C8 and 8.19
>Hi
>
>Can someone feed in :
>
>a) How much Effort is there upgrading from 7.29C8 & 8.19 ( on HP3K )
>
>b) Are there a lot of syntax changes ?
>
>c) Any major Issues ? Any precautions to be taken ?
>
>Roshan
>
>------ =_NextPart_001_01BE6FC6.AB4CFD20
>Content-Type: text/html
>
><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
><HTML>
><HEAD>
><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
><META NAME="Generator" CONTENT="MS Exchange Server version 5.5.1960.3">
><TITLE>7.29C8 and 8.19</TITLE>
></HEAD>
><BODY>
>
><P><FONT COLOR="#0000FF" SIZE=2 FACE="Arial">Hi </FONT>
></P>
>
><P><FONT COLOR="#0000FF" SIZE=2 FACE="Arial">Can someone feed in :</FONT>
></P>
>
><P><FONT COLOR="#0000FF" SIZE=2 FACE="Arial">a) How much Effort is there
>upgrading from 7.29C8 & 8.19 ( on HP3K )</FONT> </P>
>
><P><FONT COLOR="#0000FF" SIZE=2 FACE="Arial">b) Are there a lot of syntax
>changes ?</FONT> </P>
>
><P><FONT COLOR="#0000FF" SIZE=2 FACE="Arial">c) Any major Issues ? Any
>precautions to be taken ?</FONT> </P>
>
><P><FONT COLOR="#0000FF" SIZE=2 FACE="Arial">Roshan</FONT>
></P>
>
></BODY>
></HTML>
>------ =_NextPart_001_01BE6FC6.AB4CFD20--
>= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
>Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
>Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
>powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
>This list is closed, thus to post to the list, you must be a subscriber.
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
This list is closed, thus to post to the list, you must be a subscriber.