We occasionally hit this limitation with Mainframe PRO IV.
Try checking logic zero for large scratch array(s) and, if possible, reduce their size. This has been a ‘quick win’ in the past until we have had time to break the function down.
- ProIV Resource Centre
- → Viewing Profile: Posts: Los Rouse
Community Stats
- Group Members
- Active Posts 7
- Profile Views 6,363
- Member Title Newbie
- Age Age Unknown
- Birthday Birthday Unknown
-
Gender
Male
-
Location
Birmingham, England
Previous Fields
-
First Name
Los
-
Surname
Rouse
-
Nationality
English
-
Year Started ProIV
1993
-
Highest ProIV Version Used
4.0
-
Companies Worked For
As an ex-contractor the list is large :)
-
Extra Notes
I am an IBM Mainframe PRO IV Administrator. Currently (June 2003) we are on Mainframe PRO IV V4.2 and plan a test installation of V5 in Q3 of this year. Although this forum appears to be predominately for distributed boxes I hope there will still be some useful information particularly on the GUI side of things.
0
Neutral
User Tools
Friends
Los Rouse hasn't added any friends yet.
Latest Visitors
Posts I've Made
In Topic: 010 - function excedes workspace
19 November 2008 - 01:04 PM
In Topic: VARDEF - length of @VDTVL
27 June 2006 - 01:02 PM
V5.0 MF is 79 by default also... but it's Version 1.8 (MF)! We dont like to waste our money on upgrades here ..
Scott, interesting....1.8 MF I guess there was some magic happening at Y2K.
In Topic: ProIV and MQ Series
14 February 2006 - 12:24 PM
Mainframe PRO IV (Version 5) supports MQ as supplied. Maybe none mainframe PRO IV will have MQ support in the near future? It might be worth checking.
In Topic: Slow SQL execution
04 January 2005 - 01:48 PM
As a matter of interest...
On the mainframe it is good practice to use file variables for database calls where possible.
The reason being the PRO IV file layout can be generated from DB2 tables which means the variables precisely match the size/format of the columns. If a scratch variable is defined that doesn't match, say is larger, than the column then the optimiser index or tablespace scans when it might not need to. A big performance killer.
I believe this 'feature' has been fixed in DB2 v8.
On the mainframe it is good practice to use file variables for database calls where possible.
The reason being the PRO IV file layout can be generated from DB2 tables which means the variables precisely match the size/format of the columns. If a scratch variable is defined that doesn't match, say is larger, than the column then the optimiser index or tablespace scans when it might not need to. A big performance killer.
I believe this 'feature' has been fixed in DB2 v8.
In Topic: Proiv Single Developer
28 October 2004 - 04:43 PM
I downloaded Single Developer a while ago and it has been working fine for me - Windows XP Home SP2.
I just received a note from 'The Single Developer Team' saying that the version on the partner site was a beta version and that I should now download the production release. I guess I need to give this one a bash.
I just received a note from 'The Single Developer Team' saying that the version on the partner site was a beta version and that I should now download the production release. I guess I need to give this one a bash.
- ProIV Resource Centre
- → Viewing Profile: Posts: Los Rouse
- Privacy Policy