× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Does it appear in the Program Status Data Structure in any of these related
fields:
.....DName+++++++++++ETDsFrom+++To/L+++IDc
     D EXCP_MSG               40     46
 ¦   D EXCP_TYPE              40     42
 ¦   D EXCP_NUM               43     46
 ¦   D PGM_LIB                81     90
 ¦   D EXCP_DATA              91    170
 ¦   D LAST_FILE             201    208


The whole enchilada, copied and modified from the RPG/LE manual.
.....DName+++++++++++ETDsFrom+++To/L+++IDc
 ¦   DMYPSDS          SDS
 ¦   D PROC_NAME         *PROC
     D PGM               *PROC
 ¦   D PGM_STATUS        *STATUS
 ¦   D PRV_STATUS             16     20S 0
 ¦   D LINE_NUM               21     28
 ¦   D ROUTINE           *ROUTINE
 ¦   D PARMS             *PARMS
     D EXCP_MSG               40     46
 ¦   D EXCP_TYPE              40     42
 ¦   D EXCP_NUM               43     46
 ¦   D PGM_LIB                81     90
 ¦   D EXCP_DATA              91    170
 ¦   D EXCP_ID               171    174
 ¦   D PGM_DATE              191    198
 ¦   D PGM_YEAR              199    200S 0
 ¦   D LAST_FILE             201    208
 ¦   D FILE_INFO             209    243
 ¦   D JOB_NAME              244    253
     D WSID                  244    253
 ¦   D USER                  254    263
 ¦   D JOB_NUM               264    269S 0
 ¦   D JOB_DATE              270    275S 0
 ¦   D RUN_DATE              276    281S 0
 ¦   D RUN_TIME              282    287S 0
 ¦   D CRT_DATE              288    293
 ¦   D CRT_TIME              294    299
 ¦   D CPL_LEVEL             300    303
 ¦   D SRC_FILE              304    313
 ¦   D SRC_LIB               314    323
 ¦   D SRC_MBR               324    333
 ¦   D PROC_PGM              334    343
 ¦   D PROC_MOD              344    353

Rob Berendt

İİİİİİİİİİİÚ smart person learns from their mistakes,
but a wise person learns from OTHER peoples mistakes.



                    Buck Calabro
                    <Buck.Calabro@com       To:     rpg400-l@midrange.com
                    msoft.net>              cc:
                    Sent by:                Fax to:
                    rpg400-l-admin@mi       Subject:     RE: Constraint 
Violations
                    drange.com


                    10/03/2001 10:52
                    AM
                    Please respond to
                    rpg400-l






>In which area of the File Information DS does
>the name of the constraint exist?

It doesn't, which is why my error _handling_ is so lame.
Basically, I spin through the program messages looking for CPF503A and
CPF502D.  The constraint names are in the text of those messages.
  --buck





As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.