Loading...
Select Version
The INSURE database shown in the following diagram is to be restructured as follows:
the realm TRANSPORT-RLM is to be added
the record type TRANSPORT-INSURANCE is to be relocated to the realm TRANSPORT-RLM
the set CONTR-PROP with the owner record type CUSTOMER and the member record type TRANSPORT-INSURANCE is to be added
the set CLAIMS-TRANSPORT with the owner record type TRANSPORT-INSURANCE and the member record type DAMAGE-CLAIM is to be added
the record type CUSTOMER is to be modified
The diagram below shows the schema of the INSURE database after restructuring (see Figure 3, "Sample databases", for a diagram of INSURE before restructuring).
Figure 32: SHIPPINGDB database after restructuring
DBDIR, DBCOM, COSSD, HASHLIB and the user realms needed are saved before restructuring is performed (BEFRESTR). The entire database is saved after restructuring (AFTRESTR).
You should check the consistency of the database using the utility routine BCHECK before performing any save operation (see the "Recovery, Information and Reorganization" manual).
This example is only intended to illustrate the restructuring process; therefore a simple schema has been selected and the logs for Schema DDL, SSL etc. omitted.
Saving DBDIR, DBCOM, COSSD and HASHLIB
/COPY-FILE FROM-FILE=INSURE.DBDIR,TO-FILE=INSURE.DBDIR.BEFRESTR /COPY-FILE FROM-FILE=INSURE.DBCOM,TO-FILE=INSURE.DBCOM.BEFRESTR /COPY-FILE FROM-FILE=INSURE.COSSD,TO-FILE=INSURE.COSSD.BEFRESTR /COPY-FILE FROM-FILE=INSURE.HASHLIB,TO-FILE=INSURE.HASHLIB.BEFRESTR
BCHANGE run and compiling new Schema DDL and SSL
The Schema DDL in this run still contains errors. The error involved is not detected until the SSL is compiled.
/START-UDS-BCHANGE
***** START BCHANGE (UDS/SQL V2.9 1801 ) 2019-01-29 09:35:40
***** THE FILE: :IUDS:$XXXXXXXX.INSURE.DBCOM IS COPIED TO:
:IUDS:$XXXXXXXX.INSURE.DBCOM.O
***** THE FILE: :IUDS:$XXXXXXXX.INSURE.COSSD IS COPIED TO:
:IUDS:$XXXXXXXX.INSURE.COSSD.O
1006 RESTRUCTURING SUCCESSFULLY INITIATED
***** DIAGNOSTIC SUMMARY OF BCHANGE
NO WARNINGS
NO ERRORS
NO SYSTEM-ERRORS
***** END OF DIAGNOSTIC SUMMARY
***** NR OF DATABASE ACCESSES : 94
***** NORMAL END BCHANGE (UDS/SQL V2.9 1801 ) 2019-01-29 09:35:41
/CREATE-FILE FILE-NAME=INSURE.DBSTAT
/CREATE-FILE FILE-NAME=INSURE.DBSTAT.SAVE
/START-UDS-DDL
***** START DDLCOMP (UDS/SQL V2.9 1801 ) 2019-01-29 09:35:41
* DDLCOMP: INPUT SYSTEMPARAMETERS
SOURCE IS 'S.INSURE.DDL.NEW'
END
* DDLCOMP: READ SCHEMA/SUBSCHEMA
% UDS0215 UDS STARTING UDS/SQL V2.9 (LINKED-IN), DATE=2019-01-29 (ILL2038,09:35:41/4TE7)
% UDS0746 UDS PUBSET DECLARATION (CURRENT) FOLLOWS (ILL1746,09:35:41/4TE7)
4TE7: UDS-PUBSET-JV: :IUDS:$XXXXXXXX.PUBSDECL.DEFAULT
4TE7: DEFAULT PUBSET: IUDS
4TE7: ------------------------------------------
* DDLCOMP: START SCHEMA-PHASE
* DDLCOMP: CHECK SCHEMA RULES
* DDLCOMP: CHECK DATA ALLOCATION
* DDLCOMP: SEMANTIC TEST
* DDLCOMP: CYCLUS TESTS
* DDLCOMP: ERROR DIAGNOSTIC
* DDLCOMP: NO ERRORS IN SCHEMA-PHASE
* DDLCOMP: CREATE FILE COSSD
* DDLCOMP: NO ERRORS DETECTED
% UDS0758 NUMBER OF DML-STATEMENTS AND I/O COUNTERS PER DATABASE (ILL1758,09:35:42/4TE7)
4TE7: DATABASE NAME DMLS LOG READ PHYS READ LOG WRITE PHYS WRITE
4TE7: -------------------------------------------------------------------
4TE7: INSURE 651 1999 67 914 39
% UDS0213 UDS NORMAL SYSTEM TERMINATION WITH *************651 DML-STATEMENTS 2019-01-29
(ILLY033,09:35:42/4TE7)
***** DIAGNOSTIC SUMMARY FOR DDL-SCHEMA CUSTOMER-CARDS
NO ERRORS
+++++ 9 WARNINGS
***** END OF DIAGNOSTIC SUMMARY
***** NORMAL END DDLCOMP (UDS/SQL V2.9 1801 ) 2019-01-29 09:35:42
/START-UDS-SSL
***** START SSLCOMP (UDS/SQL V2.9 1801 ) 2019-01-29 09:35:42
* SSLCOMP: INPUT SYSTEMPARAMETERS
SOURCE IS 'S.INSURE.SSL.NEW'
END
* SSLCOMP: READ SSL-SCHEMA
% UDS0215 UDS STARTING UDS/SQL V2.9 (LINKED-IN), DATE=2019-01-29 (ILL2038,09:35:42/4TE7)
% UDS0746 UDS PUBSET DECLARATION (CURRENT) FOLLOWS (ILL1746,09:35:42/4TE7)
4TE7: UDS-PUBSET-JV: :IUDS:$XXXXXXXX.PUBSDECL.DEFAULT
4TE7: DEFAULT PUBSET: IUDS
4TE7: ------------------------------------------
* SSLCOMP: START SSL-PHASE
* SSLCOMP: CHECK SSL RULES
* SSLCOMP: SEMANTIC TEST
* SSLCOMP: ERROR DIAGNOSTIC
* SSLCOMP: ERRORS DETECTED IN SSL-PHASE
* SSLCOMP: ERRORS DETECTED
* SSLCOMP: ALL SSL-OPTIONS ARE RESET
+++++ ERROR: 0012 UDS-DBH RETURNS WITH DATABASE-STATUS '04021'
% UDS0758 NUMBER OF DML-STATEMENTS AND I/O COUNTERS PER DATABASE (ILL1758,09:35:42/4TE7)
4TE7: DATABASE NAME DMLS LOG READ PHYS READ LOG WRITE PHYS WRITE
4TE7: -------------------------------------------------------------------
4TE7: INSURE 303 387 61 71 25
% UDS0213 UDS NORMAL SYSTEM TERMINATION WITH *************303 DML-STATEMENTS 2019-01-29
(ILLY033,09:35:42/4TE7)
***** DIAGNOSTIC SUMMARY FOR SSL - SCHEMA
+++++ 2 ERRORS
NO WARNINGS
***** END OF DIAGNOSTIC SUMMARY
+++++ ABNORMAL END SSLCOMP (UDS/SQL V2.9 1801 ) 2019-01-29 09:35:42
Compiling the corrected schema
Once you have corrected the Schema DDL according to the SSL-ERROR-DIAGNOSTIC, you must delete the errored schema that has already been entered. Only then can you compile the corrected Schema DDL and then the SSL.
/START-UDS-DDL
***** START DDLCOMP (UDS/SQL V2.9 1801 ) 2019-01-29 09:35:42
* DDLCOMP: INPUT SYSTEMPARAMETERS
DELETE SCHEMA 'CUSTOMER-CARDS'
END
% UDS0215 UDS STARTING UDS/SQL V2.9 (LINKED-IN), DATE=2019-01-29 (ILL2038,09:35:42/4TE7)
% UDS0746 UDS PUBSET DECLARATION (CURRENT) FOLLOWS (ILL1746,09:35:43/4TE7)
4TE7: UDS-PUBSET-JV: :IUDS:$XXXXXXXX.PUBSDECL.DEFAULT
4TE7: DEFAULT PUBSET: IUDS
4TE7: ------------------------------------------
* DDLCOMP: SCHEMA HAS BEEN ERASED
* DDLCOMP: NO ERRORS DETECTED
% UDS0758 NUMBER OF DML-STATEMENTS AND I/O COUNTERS PER DATABASE (ILL1758,09:35:43/4TE7)
4TE7: DATABASE NAME DMLS LOG READ PHYS READ LOG WRITE PHYS WRITE
4TE7: -------------------------------------------------------------------
4TE7: INSURE 6 1075 70 556 39
% UDS0213 UDS NORMAL SYSTEM TERMINATION WITH ***************6 DML-STATEMENTS 2019-01-29
(ILLY033,09:35:43/4TE7)
***** NORMAL END DDLCOMP (UDS/SQL V2.9 1801 ) 2019-01-29 09:35:43
/START-UDS-DDL
***** START DDLCOMP (UDS/SQL V2.9 1801 ) 2019-01-29 09:35:43
* DDLCOMP: INPUT SYSTEMPARAMETERS
SOURCE IS 'S.INSURE.DDL.KORR'
DISPLAY IS YES
END
* DDLCOMP: READ SCHEMA/SUBSCHEMA
% UDS0215 UDS STARTING UDS/SQL V2.9 (LINKED-IN), DATE=2019-01-29 (ILL2038,09:35:43/4TE7)
% UDS0746 UDS PUBSET DECLARATION (CURRENT) FOLLOWS (ILL1746,09:35:43/4TE7)
4TE7: UDS-PUBSET-JV: :IUDS:$XXXXXXXX.PUBSDECL.DEFAULT
4TE7: DEFAULT PUBSET: IUDS
4TE7: ------------------------------------------
* DDLCOMP: START SCHEMA-PHASE
* DDLCOMP: CHECK SCHEMA RULES
* DDLCOMP: CHECK DATA ALLOCATION
* DDLCOMP: SEMANTIC TEST
* DDLCOMP: CYCLUS TESTS
* DDLCOMP: ERROR DIAGNOSTIC
* DDLCOMP: NO ERRORS IN SCHEMA-PHASE
* DDLCOMP: DISPLAY SCHEMA
* DDLCOMP: CREATE FILE COSSD
* DDLCOMP: NO ERRORS DETECTED
% UDS0758 NUMBER OF DML-STATEMENTS AND I/O COUNTERS PER DATABASE (ILL1758,09:35:43/4TE7)
4TE7: DATABASE NAME DMLS LOG READ PHYS READ LOG WRITE PHYS WRITE
4TE7: -------------------------------------------------------------------
4TE7: INSURE 751 2120 66 914 40
% UDS0213 UDS NORMAL SYSTEM TERMINATION WITH *************751 DML-STATEMENTS 2019-01-29
(ILLY033,09:35:44/4TE7)
***** DIAGNOSTIC SUMMARY FOR DDL-SCHEMA CUSTOMER-CARDS
NO ERRORS
+++++ 9 WARNINGS
***** END OF DIAGNOSTIC SUMMARY
***** NORMAL END DDLCOMP (UDS/SQL V2.9 1801 ) 2019-01-29 09:35:44
/START-UDS-SSL
***** START SSLCOMP (UDS/SQL V2.9 1801 ) 2019-01-29 09:35:44
* SSLCOMP: INPUT SYSTEMPARAMETERS
SOURCE IS 'S.INSURE.SSL.NEW'
END
* SSLCOMP: READ SSL-SCHEMA
% UDS0215 UDS STARTING UDS/SQL V2.9 (LINKED-IN), DATE=2019-01-29 (ILL2038,09:35:44/4TE7)
% UDS0746 UDS PUBSET DECLARATION (CURRENT) FOLLOWS (ILL1746,09:35:44/4TE7)
4TE7: UDS-PUBSET-JV: :IUDS:$XXXXXXXX.PUBSDECL.DEFAULT
4TE7: DEFAULT PUBSET: IUDS
4TE7: ------------------------------------------
* SSLCOMP: START SSL-PHASE
* SSLCOMP: CHECK SSL RULES
* SSLCOMP: SEMANTIC TEST
* SSLCOMP: ERROR DIAGNOSTIC
* SSLCOMP: NO ERRORS DETECTED
% UDS0758 NUMBER OF DML-STATEMENTS AND I/O COUNTERS PER DATABASE (ILL1758,09:35:44/4TE7)
4TE7: DATABASE NAME DMLS LOG READ PHYS READ LOG WRITE PHYS WRITE
4TE7: -------------------------------------------------------------------
4TE7: INSURE 127 253 63 34 23
% UDS0213 UDS NORMAL SYSTEM TERMINATION WITH *************127 DML-STATEMENTS 2019-01-29
(ILLY033,09:35:44/4TE7)
***** DIAGNOSTIC SUMMARY FOR SSL - SCHEMA
NO ERRORS
NO WARNINGS
***** END OF DIAGNOSTIC SUMMARY
***** NORMAL END SSLCOMP (UDS/SQL V2.9 1801 ) 2019-01-29 09:35:44
/DELETE-SYSTEM-FILE FILE-NAME=*OMF
/START-UDS-BGSIA
***** START BGSIA (UDS/SQL V2.9 1801 ) 2019-01-29 09:35:44
GENERATE SCHEMA CUSTOMER-CARDS
DISPLAY
END
% UDS0215 UDS STARTING UDS/SQL V2.9 (LINKED-IN), DATE=2019-01-29 (ILL2038,09:35:44/4TE7)
% UDS0746 UDS PUBSET DECLARATION (CURRENT) FOLLOWS (ILL1746,09:35:44/4TE7)
4TE7: UDS-PUBSET-JV: :IUDS:$XXXXXXXX.PUBSDECL.DEFAULT
4TE7: DEFAULT PUBSET: IUDS
4TE7: ------------------------------------------
ESTIMATE-REPORT
********** FOR USER-REALM 3 NAME IS : PROP-RLM
A SIZE OF 24 BLOCKS WAS ESTIMATED
********** FOR USER-REALM 4 NAME IS : INSURE-RLM
A SIZE OF 239 BLOCKS WAS ESTIMATED
********** FOR USER-REALM 6 NAME IS : TRANSPORT-RLM
A SIZE OF 24 BLOCKS WAS ESTIMATED
END OF ESTIMATE-REPORT
% UDS0758 NUMBER OF DML-STATEMENTS AND I/O COUNTERS PER DATABASE (ILL1758,09:35:45/4TE7)
4TE7: DATABASE NAME DMLS LOG READ PHYS READ LOG WRITE PHYS WRITE
4TE7: -------------------------------------------------------------------
4TE7: INSURE 569 779 60 183 30
% UDS0213 UDS NORMAL SYSTEM TERMINATION WITH *************569 DML-STATEMENTS 2019-01-29
(ILLY033,09:35:45/4TE7)
***** DIAGNOSTIC SUMMARY OF BGSIA
NO WARNINGS
NO ERRORS
NO SYSTEM-ERRORS
***** END OF DIAGNOSTIC SUMMARY
***** NORMAL END BGSIA (UDS/SQL V2.9 1801 ) 2019-01-29 09:35:45
/MODIFY-JOB-SWITCHES ON=(4)
/START-LMS
//MODIFY-LOGGING-PARAMETERS LOG=*MAX
//OPEN-LIBRARY LIB=INSURE.HASHLIB,MODE=*UPDATE
//ADD-ELEMENT FROM-FILE=*OMF,TO-ELEM=*LIB-ELEM(TYPE=R),WRITE-MODE=*ANY
INPUT OMF
OUTPUT LIBRARY= :IUDS:$XXXXXXXX.INSURE.HASHLIB
ADD UDSHASH AS (R)UDSHASH/@(0002)/2019-01-29 , OUTPUT REPLACED
//SHOW-ELEM-ATTR
INPUT LIBRARY= :IUDS:$XXXXXXXX.INSURE.HASHLIB
TYP NAME VER (VAR#) DATE NAME VER (VAR#) DATE
(R) ADMIN## @ (0001) 2019-01-29 UDSHASH @ (0002) 2019-01-29
2 (R)-ELEMENT(S) IN THIS TABLE OF CONTENTS
//END
/MODIFY-JOB-SWITCHES OFF=(4)
Analysis phase with REPORT IS YES and EXECUTION IS NO
/START-UDS-BALTER
***** START BALTER (UDS/SQL V2.9 1801 ) 2019-01-29 09:35:45
REPORT IS YES.
EXECUTION IS NO.
END.
*** ANALYSE-PHASE ***
*** DATE AND TIME 2019-01-29 09:35:45
+++++ WARNING: 1081 AREAS DELETED FROM RECORD-WITHIN-CLAUSE
RECORD: TRANSPORT-INSURANCE
IF RECORD OCCURRENCES ARE PRESENT IN AREAS
WHICH ARE DELETED FROM RECORD-WITHIN-CLAUSE
THE RESTRUCTURING PROCESS WILL END ABNORMALLY.
NO ERRORS DETECTED IN SCHEMA CHANGES
*** REPORT-PHASE ***
*** DATE AND TIME 2019-01-29 09:35:45
REALM NOT NEEDED: PROP-RLM
REALM NEEDED: INSURE-RLM
DATABASE NOT ALTERED
NUMBER OF FILE ACCESSES: 0
***** DIAGNOSTIC SUMMARY OF BALTER
+++++ 1 WARNINGS
NO ERRORS
NO SYSTEM-ERRORS
***** END OF DIAGNOSTIC SUMMARY
***** NR OF DATABASE ACCESSES : 107
***** NORMAL END BALTER (UDS/SQL V2.9 1801 ) 2019-01-29 09:35:45
Since the database does not include a record of the record type TRANSPORT-INSURANCE, the warning can be ignored and the database restructured.
Of the two user realms INSURE.PROP-RLM and INSURE.INSURE-RLM, only INSURE.INSURE-RLM is needed for the restructuring process.
This realm is saved:
/COPY-FILE FROM-FILE=INSURE.INSURE-RLM, TO-FILE=INSURE.INSURE-RLM.BEFRESTR
Restructuring phase
/CREATE-FILE FILE-NAME=INSURE.TRANSPORT-RLM,SUPPORT=*PUBLIC-DISK( -
/ PRIMARY-ALLOCATION=50,SECONDARY-ALLOCATION=50)
/START-UDS-BALTER
***** START BALTER (UDS/SQL V2.9 1801 ) 2019-01-29 09:35:45
REPORT IS NO .
EXECUTION IS YES.
END.
*** ANALYSE-PHASE ***
*** DATE AND TIME 2019-01-29 09:35:45
+++++ WARNING: 1081 AREAS DELETED FROM RECORD-WITHIN-CLAUSE
RECORD: TRANSPORT-INSURANCE
IF RECORD OCCURRENCES ARE PRESENT IN AREAS
WHICH ARE DELETED FROM RECORD-WITHIN-CLAUSE
THE RESTRUCTURING PROCESS WILL END ABNORMALLY.
NO ERRORS DETECTED IN SCHEMA CHANGES
*** EXECUTION-PHASE ***
*** DATE AND TIME 2019-01-29 09:35:45
REALM ADDED TO DATABASE: TRANSPORT-RLM
*** DATE AND TIME 2019-01-29 09:35:46
MODIFICATION CONCERNING OWNER ATTRIBUTE STARTED FOR
REC NAME: TRANSPORT-INSURANCE
REC REF: 3
*** DATE AND TIME 2019-01-29 09:35:46
MODIFICATION CONCERNING OWNER ATTRIBUTE STARTED FOR
REC NAME: CUSTOMER
REC REF: 4
*** DATE AND TIME 2019-01-29 09:35:46
RECORD MODIFICATION STARTED FOR:
REC NAME: TRANSPORT-INSURANCE
REC REF: 3
*** DATE AND TIME 2019-01-29 09:35:46
RECORD MODIFICATION STARTED FOR:
REC NAME: CUSTOMER
REC REF: 4
*** DATE AND TIME 2019-01-29 09:35:46
RECORD MODIFICATION STARTED FOR:
REC NAME: DAMAGE-CLAIM
REC REF: 5
*** DATE AND TIME 2019-01-29 09:35:46
DATABASE ALTERED
*** DATE AND TIME 2019-01-29 09:35:46
NUMBER OF FILE ACCESSES: 10
***** DIAGNOSTIC SUMMARY OF BALTER
+++++ 1 WARNINGS
NO ERRORS
NO SYSTEM-ERRORS
***** END OF DIAGNOSTIC SUMMARY
***** NR OF DATABASE ACCESSES : 248
***** NORMAL END BALTER (UDS/SQL V2.9 1801 ) 2019-01-29 09:35:46
Entering new access rights
/START-UDS-BPRIVACY
***** START BPRIVACY (UDS/SQL V2.9 1801 ) 2019-01-29 09:35:46
% UDS0215 UDS STARTING UDS/SQL V2.9 (LINKED-IN), DATE=2019-01-29 (ILL2038,09:35:46/4TE7)
% UDS0746 UDS PUBSET DECLARATION (CURRENT) FOLLOWS (ILL1746,09:35:46/4TE7)
4TE7: UDS-PUBSET-JV: :IUDS:$XXXXXXXX.PUBSDECL.DEFAULT
4TE7: DEFAULT PUBSET: IUDS
4TE7: ------------------------------------------
% UDS0722 UDS ORDER ADD RLOG 190129083546 IN EXECUTION (ILL1283,09:35:46/4TE7)
% UDS0356 UDS EXECUTION OF ORDERS FOR INSURE TERMINATED (ILL1309,09:35:46/4TE7)
//ADD-USER-GROUP USER-GROUP-NAME=*FREE-FORMAT(HOST=IBAPROD1,USER-ID=XXXXXXXX), -
// OBJECT=(*REALM(NAME=*ALL,RIGHT=ALL),*RECORD(NAME=*ALL,RIGHT=ALL), -
// *SET(NAME=*ALL,RIGHT=ALL))
//END
% UDS0758 NUMBER OF DML-STATEMENTS AND I/O COUNTERS PER DATABASE (ILL1758,09:35:46/4TE7)
4TE7: DATABASE NAME DMLS LOG READ PHYS READ LOG WRITE PHYS WRITE
4TE7: ------------------------------------------------------------------------
4TE7: INSURE 11 115 57 36 23
% UDS0213 UDS NORMAL SYSTEM TERMINATION WITH **************11 DML-STATEMENTS 2019-01-29
(ILLY033,09:35:46/4TE7)
***** DIAGNOSTIC SUMMARY OF BPRIVACY
NO WARNINGS
NO ERRORS
NO SYSTEM-ERRORS
***** END OF DIAGNOSTIC SUMMARY
***** NORMAL END BPRIVACY (UDS/SQL V2.9 1801 ) 2019-01-29 09:35:46
Testing whether the subschema is compatible with the new schema
/START-UDS-DDL ***** START DDLCOMP (UDS/SQL V2.9 1801 ) 2019-01-29 09:35:46 * DDLCOMP: INPUT SYSTEMPARAMETERS COMPARE SUBSCHEMAS DIAGNOSTIC IS YES END % UDS0215 UDS STARTING UDS/SQL V2.9 (LINKED-IN), DATE=2019-01-29 (ILL2038,09:35:46/4TE7) % UDS0746 UDS PUBSET DECLARATION (CURRENT) FOLLOWS (ILL1746,09:35:46/4TE7) 4TE7: UDS-PUBSET-JV: :IUDS:$XXXXXXXX.PUBSDECL.DEFAULT 4TE7: DEFAULT PUBSET: IUDS 4TE7: ------------------------------------------ * DDLCOMP: READ SCHEMA/SUBSCHEMA 1 * DDLCOMP: START SUBSCHEMA-PHASE * DDLCOMP: CHECK SUBSCHEMA RULES * DDLCOMP: CHECK DATA ALLOCATION * DDLCOMP: SUBCOPY * DDLCOMP: ERROR DIAGNOSTIC * DDLCOMP: ERRORS DETECTED IN SUBSCHEMA-PHASE * DDLCOMP: SUBSCHEMA HAS BEEN ERASED % UDS0758 NUMBER OF DML-STATEMENTS AND I/O COUNTERS PER DATABASE (ILL1758,09:35:47/4TE7) 4TE7: DATABASE NAME DMLS LOG READ PHYS READ LOG WRITE PHYS WRITE 4TE7: ------------------------------------------------------------------- 4TE7: INSURE 832 2616 74 936 44 % UDS0213 UDS NORMAL SYSTEM TERMINATION WITH *************832 DML-STATEMENTS 2019-01-29 (ILLY033,09:35:47/4TE7) ***** DIAGNOSTIC SUMMARY FOR DDL-SUBSCHEMA +++++ 1 ERRORS +++++ 9 WARNINGS ***** END OF DIAGNOSTIC SUMMARY ***** NORMAL END DDLCOMP (UDS/SQL V2.9 1801 ) 2019-01-29 09:35:47
Modifying the subschema
Since the old Subschema DDL is not compatible with the new Schema DDL, the Subschema DDL is corrected and then recompiled.
/START-UDS-DDL
***** START DDLCOMP (UDS/SQL V2.9 1801 ) 2019-01-29 09:35:47
* DDLCOMP: INPUT SYSTEMPARAMETERS
SOURCE IS 'S.INSURE.SUBDDL.NEW'
END
* DDLCOMP: READ SCHEMA/SUBSCHEMA
% UDS0215 UDS STARTING UDS/SQL V2.9 (LINKED-IN), DATE=2019-01-29 (ILL2038,09:35:47/4TE7)
% UDS0746 UDS PUBSET DECLARATION (CURRENT) FOLLOWS (ILL1746,09:35:47/4TE7)
4TE7: UDS-PUBSET-JV: :IUDS:$XXXXXXXX.PUBSDECL.DEFAULT
4TE7: DEFAULT PUBSET: IUDS
4TE7: ------------------------------------------
* DDLCOMP: START SUBSCHEMA-PHASE
* DDLCOMP: CHECK SUBSCHEMA RULES
* DDLCOMP: CHECK DATA ALLOCATION
* DDLCOMP: SUBCOPY
* DDLCOMP: ERROR DIAGNOSTIC
* DDLCOMP: NO ERRORS IN SUBSCHEMA-PHASE
* DDLCOMP: WRITE SUBSCHEMA ON COSSD
* DDLCOMP: NO ERRORS DETECTED
% UDS0758 NUMBER OF DML-STATEMENTS AND I/O COUNTERS PER DATABASE (ILL1758,09:35:48/4TE7)
4TE7: DATABASE NAME DMLS LOG READ PHYS READ LOG WRITE PHYS WRITE
4TE7: -------------------------------------------------------------------
4TE7: INSURE 1363 2581 76 631 49
% UDS0213 UDS NORMAL SYSTEM TERMINATION WITH ************1363 DML-STATEMENTS 2019-01-29
(ILLY033,09:35:48/4TE7)
***** DIAGNOSTIC SUMMARY FOR DDL-SUBSCHEMA
NO ERRORS
NO WARNINGS
***** END OF DIAGNOSTIC SUMMARY
***** NORMAL END DDLCOMP (UDS/SQL V2.9 1801 ) 2019-01-29 09:35:48
/START-UDS-BGSSIA
***** START BGSSIA (UDS/SQL V2.9 1801 ) 2019-01-29 09:35:48
GENERATE SUBSCHEMA MANAGEMENT OF SCHEMA CUSTOMER-CARDS
DISPLAY
END
% UDS0215 UDS STARTING UDS/SQL V2.9 (LINKED-IN), DATE=2019-01-29 (ILL2038,09:35:48/4TE7)
% UDS0746 UDS PUBSET DECLARATION (CURRENT) FOLLOWS (ILL1746,09:35:48/4TE7)
4TE7: UDS-PUBSET-JV: :IUDS:$XXXXXXXX.PUBSDECL.DEFAULT
4TE7: DEFAULT PUBSET: IUDS
4TE7: ------------------------------------------
*** SSIA GENERATION NORMALLY ENDED.
*GENERATION OF ITEM-TABLE AND NAME-TABLE STARTED.
*GENERATION OF ITEM-TABLE AND NAME-TABLE FINISHED.
% UDS0758 NUMBER OF DML-STATEMENTS AND I/O COUNTERS PER DATABASE (ILL1758,09:35:48/4TE7)
4TE7: DATABASE NAME DMLS LOG READ PHYS READ LOG WRITE PHYS WRITE
4TE7: -------------------------------------------------------------------
4TE7: INSURE 781 1359 76 286 29
% UDS0213 UDS NORMAL SYSTEM TERMINATION WITH *************781 DML-STATEMENTS 2019-01-29
(ILLY033,09:35:48/4TE7)
***** DIAGNOSTIC SUMMARY OF BGSSIA
NO WARNINGS
NO ERRORS
NO SYSTEM-ERRORS
***** END OF DIAGNOSTIC SUMMARY
***** NORMAL END BGSSIA (UDS/SQL V2.9 1801 ) 2019-01-29 09:35:48
The restructuring of the database has now been completed.
Now, of course, the DB application programs have to be modified if they reference the modified items and have to be recompiled and linked again due to the incompatibility between the old and new subschemas.
Reorganizing the restructured database
To save memory space, the hash area for the record type CUSTOMER is reorganized, i.e. moved back to the area that is now free at the front of the realm. This means that the size of INSURE-RLM can be minimized.
/START-UDS-BREORG
***** START BREORG (UDS/SQL V2.9 1801 ) 2019-01-29 09:35:48
//SPECIFY-SCHEMA SCHEMA-NAME=CUSTOMER-CARDS
//REORGANIZE-CALC RECORD-NAME=CUSTOMER,
CALC-RECORD=*WITHIN-POPULATION(REALM=INSURE-RLM,POPULATION=500),CALC-SEARCHKEY=NONE
//END
***** BEGIN OF CALC-REORGANIZATION AT 09:35:49
***** RESULTS OF CALC-REORGANIZATION OF RECORD CUSTOMER
NEW CALC BEGIN : 4- 5
NEW NR OF PRIMARY BUCKETS : 59
NEW NR OF OVERFLOW BUCKETS: 0
***** END OF CALC-REORGANIZATION AT 09:35:49
***** DIAGNOSTIC SUMMARY OF BREORG
NO WARNINGS
NO ERRORS
NO SYSTEM-ERRORS
***** END OF DIAGNOSTIC SUMMARY
***** NR OF DATABASE ACCESSES : 77
***** NORMAL END BREORG (UDS/SQL V2.9 1801 ) 2019-01-29 09:35:49
/START-UDS-BREORG
***** START BREORG (UDS/SQL V2.9 1801 ) 2019-01-29 09:35:49
//SPECIFY-SCHEMA SCHEMA-NAME=CUSTOMER-CARDS
//MODIFY-REALM-SIZE REALM-NAME=INSURE-RLM,REALM-SIZE=MINIMUM
//END
***** BEGIN OF REALM-SIZE-MODIFICATION AT 09:35:50
***** RESULTS OF FPA-REORGANIZATION OF AREA INSURE-RLM
NEW FPA FIRST PAGE : NOT CHANGED
NEW FPA LAST PAGE : NOT CHANGED
NEW FPA SIZE : NOT CHANGED
NEW NR OF PAGES : 80
***** END OF REALM-SIZE-MODIFICATION AT 09:35:50
***** DIAGNOSTIC SUMMARY OF BREORG
NO WARNINGS
NO ERRORS
NO SYSTEM-ERRORS
***** END OF DIAGNOSTIC SUMMARY
***** NR OF DATABASE ACCESSES : 70
***** NORMAL END BREORG (UDS/SQL V2.9 1801 ) 2019-01-29 09:35:50
Measures to be taken before resuming database operation
A shadow database with the suffix AFTRESTR is created. The data saved before restructuring took place is deleted along with the files INSURE.DBCOM.O and INSURE.COSSD.O.
/COPY-FILE FROM-FILE=INSURE.HASHLIB,TO-FILE=INSURE.HASHLIB.AFTRESTR
/COPY-FILE FROM-FILE=INSURE.COSSD ,TO-FILE=INSURE.COSSD.AFTRESTR
/COPY-FILE FROM-FILE=INSURE.DBDIR ,TO-FILE=INSURE.DBDIR.AFTRESTR
/COPY-FILE FROM-FILE=INSURE.DBCOM ,TO-FILE=INSURE.DBCOM.AFTRESTR
/COPY-FILE FROM-FILE=INSURE.PROP-RLM,TO-FILE=INSURE.PROP-RLM.AFTRESTR
/COPY-FILE FROM-FILE=INSURE.INSURE-RLM,TO-FILE=INSURE.INSURE-RLM.AFTRESTR
/COPY-FILE FROM-FILE=INSURE.TRANSPORT-RLM,TO-FILE=INSURE.TRANSPORT-RLM.AFTRESTR
/DELETE-FILE FILE-NAME=INSURE*BEFRESTR*
/DELETE-FILE FILE-NAME=INSURE.DBCOM.O
/DELETE-FILE FILE-NAME=INSURE.COSSD.O