Jump to content


nurquhar

Member Since 22 Nov 2005
Offline Last Active Mar 10 2010 07:38 AM
-----

Topics I've Started

Kernal Error for simple GS REGEN

02 March 2010 - 11:21 AM

Using PRO-IV v4 on AIX

I get this message when regening a simple Global Screen (as below).

200 - INTERNAL KERNEL ERROR - REGEN FUNCTION

The problem seems to be caused in some way by adding a Parameter to the Global Function. i.e. With a Parameter of "Both,$FLD,A6" I get the Kernal Error. If I delete the parameter the function will regen and run. I does'nt seem to mater what type of parameter I add, be it In/Out or Both or Alpha or Numeric.

McDonnell Information Systems
TRM: PTS_26 F U N C T I O N D O C U M E N T A T I O N OPR: NA


FUNCTION NAME: gs 'SCREEN' Global Screen


FUNCTION DEFINITION
REV#: 4.0000
FUNCTION NAME: gs TITLE: Global Screen
TYPE: G SPECS CHG ON: 02/03/10 RESET ON: 02/03/10
EXIT LINK: ERROR LINK: 10:55:38
LOGIC IN: LOGIC OUT: NO CMD CALL:
ANALYST: SIZES: 74 PSB:
ENTRY DATE: 02/03/10 BY: NAU


MENU TYPE:
ICON LABEL:
ICON NAME:
SUPPRESS LINES 1 & 2 :
MENU NAME 1 : LEGEND:
2 :
3 :
4 :
5 :
6 :
7 :
8 :
9 :
10 :




PRINTING FORMAT
SEQ# ------------------------ D E S C R I P T I O N ----------------------



FUNCTION NAME: gs 'SCREEN' Global Screen


SCREEN IMAGE

SCREEN FORMAT ID:


1 2 3 4 5 6 7
1234567890123456789012345678901234567890123456789012345678901234567890123456
----------------------------------------------------------------------------
01:
02: 02/03/10 200/NAU/PTS
03:
04:
05:
06:
07:
08:
09:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
----------------------------------------------------------------------------
1234567890123456789012345678901234567890123456789012345678901234567890123456
1 2 3 4 5 6 7



PRINTING FIELD SPECS

SCREEN FIELD DEFINITION

-------------------------------------------------------------------------------
A FIL LGC SPECIAL GEN LGC M N D A O T SEC LK
FLD VAR LN B COL CDE DISPLAY-CODE LEN BEF CHECK CHK AFT I C O R V B L C SF
--- --- -- - --- --- ------------ ---- --- -------- --- --- - - - - - - - - --
001 $FLD
CHARACTERISTICS 1 1 6


SCREEN CHARACTERISTICS DEFINITION

---------------------------LOGICAL SCREEN INFORMATION--------------------------
SCREEN# : 01 DEF LOGIC : EXIT LOGIC : ONE TIME :
FORMAT ID : CLEAR CRT : LS MODE(S) : C DEF MODE : C
START FLD# : 1 END FIELD# : 1 LAST RD FLD:
MODE LINE : LNE# PRMPT :
SUPP WIND: ENT LGC: EOD-CANLGC: SUPP AYS?:
LKUP DEL: LS UPDATE: EXP/CONT DEF: EXP/CONT SUPP:
ITER COUNT:


LS PLACEMENT- STRT ROW: STRT COL: ROWS: COLS:
P A G I N G: STRT ROW: STRT COL: ROWS: COLS:
#LNS/RCD: #COL/RCD: PG ARRAY: # ELMNTS:
CONTRACTED - END FLD : #CTD LNS:
S O R T : SSEL LGC: SSEL EFL: VAR1:
VAR2: VAR3:
VAR4: VAR5:


PRINTING ERROR MESSAGES

GLOBAL FUNCTION INTERFACE PARAMETERS

SEQ PARM TYPE PARAMETER VARIABLE NAME VAR TYPE LEN ARRAY SIZE
--- --------- -------------------------------- -------- --- ----------
001 B $FLD A 6


E N D O F D O C U M E N T A T I O N FOR gs



Currious Alt Keys error message from @F

12 February 2010 - 10:20 AM

Using PRO-IV v4 on AIX

I have defined a new Cisam file in @F (SPSTR01M) which has a an alternate key called SPSTR01L.

On exiting the @F screen I get the following warning when it creates the Alt File Defs :

Alternate name already being used by another file 'SPSTR01L'.


Now we did have a Cisam file defined called SPSTR01L but I have deleted the file defenition so I can't see where the name clash is that the error implies.

As an additional check I built myself a little util to list all the Alt Keys define in FILEDEF with an MS var type. I did'nt find any other files with Alt keys of the same name.

So if no references to SPSTR01L are left in FILEHDR or FILEDEF where else could @F be finding a name clash ? Does PRO-IV store the Alt Key name in any other bootstraps which need to be purged ?

This is my abbreviated file def :



Change @F
12/02/10 FILE DEFINITION 200/NAU/PTS_28


CO- AUTO EXTERNAL FILE KEY RECORD
DIV SEQUENCED RECORD FORMAT TYPE LENGTH LENGTH
FILE NAME: SPSTR01M Y Cisam 6 174
ALTERNATE: ../altdata/so/spstr01m RECORD CODE: MSG:
DESC: Stock roll details
Change
-------------------------- R E C O R D L A Y O U T -------------------------
DATA MAX FILL SPECIAL ARRY
SEQ TYPE VARIABLE NAME LEN CODE DISPLAY-CODE CHECK SIZE
--- ---- -------------------------------- ---- ---- ------------ -------- ----
001 K SPSTR01L.ROLL.NO 6 LFZ UPPERINP
002 A SPPDT01M.CODE 20 UPPERINP
003 A SPSTR01L.BRANCH 3 UPPERINP
004 N SPSTR01L.ORIG.LENGTH 7 'ZZ9.999'
005 N SPSTR01L.ORIG.WIDTH 7 'ZZZ9.99'
.
.
021 A SPSTR01L.ADD.ON.NARRATIVE 40
022 MS SPSTR01L
023 M SPPDT01M.CODE 1 20
024 M SPSTR01L.BRANCH 1 3
025 M SPSTR01L.ROLL.NO 1 6
026 ME
027 MS SPSTR02L
028 M SPSTR01L.BRANCH 1 3
029 M SPPDT01M.CODE 1 20
030 M SPSTR01L.ROLL.NO 1 6
031 ME
032 MS SPSTR03L
033 M SPSTR01L.DEAD 1 1
034 M SPSTR01L.BRANCH 1 3
035 M SPPDT01M.CODE 1 20
036 M SPSTR01L.ROLL.NO 1 6
037 ME


Can WINLOCATE be given row,col relative to a pageing record ?

11 December 2009 - 04:08 PM

Using Pro-IV v4 on AIX

Although @PSEQ and @FLD enables me to determine the current record and field in a paging screen, is there anyway of finding out which line on the screen the current record is positioned at ? I am looking to use WINLOCATE to position a window relative to the current record in a paging screen. However WINLOCATE uses absolute coords.

I did wonder if it might be posible to use some kind of relative position tracking by looking the difference between @PSEQ and @CPSEQ in ARNE logic of the primary file but fear this would not work when the user types his required record number in the @PSEQ field.

Any Ideas ?

Anybody got Ver 4.0 Bootstrap file defs ?

05 January 2006 - 12:27 PM

I am working on customers site who is still using V4.0 (green screen on IBM AIX). Since I am trying to add one or two of my own utilities I find that the customers bootstrap filedefs are either missing of from a previous version. ie FUNCTDEF has @FUNT with a Length of 1. On 4.0 this should be 2 so I can't trust any of the boostrap filedefs present. This makes it impossible to gen any utils that modify the bootstraps without them potentialy corrupting the system.

Has anybody got a PRX of the 4.0 Bootstraps they could send me (neil@nusoft.co.uk) or post somewhere ? Might be good to do isout on the prx to be sure.

Regards
Neil

Where is PFKEYUSAGE() text defined ?

23 November 2005 - 12:46 PM

You can use PKKEYCAP() to get the key legend defined in $CRT, this works fine. However after searching the documentation I can't find any mention of where the text returned by PFKEYUSAGE() is in fact defined. Is it in some "hidden" window somewhere, does anybody know ?

Regards
Neil