VisualAge Pacbase AIX, HP-UX, Sun Solaris, HP Tru64 Unix 3.5 Y04C (CSD) E

Technote (FAQ)


Question

List of changes of the VisualAge Pacbase AIX, HP-UX, Sun Solaris, HP Tru64 Unix 3.5 Y04C version

Answer


VISUALAGE PACBASE AIX 3.5 Y04C(CSD)

NEW FUNCTIONALITIES

Batch System Development

New generation limit for GCP and GCD: a segment can now contain 9999 data elements (C:030231)
Generation of programs or copy clause.
For the generation, a segment can now contain up to 9999 data elements (before, the limit was 999).
The number of input lines in the -CE of the segment has not been modified.
An error message is printed in the GPRT output report if this limit has been exceeded.
The segment statistics screen (-STA) now correctly displays the counters.

Generated programs

New generation limit for GCP and GCD: a segment can now contain 9999 data elements (C:030231)
Generation of programs or copy clause.
For the generation, a segment can now contain up to 9999 data elements (before, the limit was 999).
The number of input lines in the -CE of the segment has not been modified.
An error message is printed in the GPRT output report if this limit has been exceeded.
The segment statistics screen (-STA) now correctly displays the counters.

Security Systems Interface

TUI access: the user code can be different from the system sign-on user code. (C:030144)
TUI access: the user code can be different from the system sign-on user code.
In Administrator workbench, in the security browser, a new tab allows to specify the authorization to connect with a user code different from the system one for a database under RACF control.
On the sign-on screen of VisualAge Pacbase, if the database is under RACF control, the user code and password can be entered if the authorization to connect with another user is set in the security browser.

Miscellaneous : Online

TUI access: the user code can be different from the system sign-on user code. (C:030144)
TUI access: the user code can be different from the system sign-on user code.
In Administrator workbench, in the security browser, a new tab allows to specify the authorization to connect with a user code different from the system one for a database under RACF control.
On the sign-on screen of VisualAge Pacbase, if the database is under RACF control, the user code and password can be entered if the authorization to connect with another user is set in the security browser.

CORRECTED BUGS

Administration

Initialization of the password validity duration in the security browser (C:030164)
Initialization of the password validity duration in the security browser.
In the supplied administrator database, the indicator of password validity duration is now checked to "unlimited" and the field "Number of validity days" is protected.

Batch

UPDT: when a definition with a keyword is deleted, the timestamp is deleted (C:030099)
UPDT: when a definition with a keyword was deleted, the timestamp was wrongly kept.
It is now deleted.

Batch System Development

Correct management of the '.' back to the MCI operator in the batch and online generators (C:028648)
Correct management of the '.' back to the MCI operator for the GCP and GCO generations.

GCP / CASE OF: the values input after the 'IT' are no more truncated (C:030040)
GCP / CASE OF: the values input after the 'IT' are no more truncated.
The IT instruction that follows the CASE OF is now generated on 2 lines in order to avoid the truncation problems.

The options in the -GO screen of a database block do not trouble the generation anymore (C:030190)
The options in the -GO screen of a database block do not trouble the generation anymore.
1. If a program with a '2'-type organization segment had an associated block (specified in the 'EXTERN' field) with at least one option in its -GO screen, the generated program was incomplete (segments of the -CD and specific processing not generated !!):
This has been corrected.

2. For the GCO, GGS and GGC commands, the DESCR=ALL option (-GO of the block) was ignored when it was preceded by an option.
This is also corrected.

GCO: Occursed Data Elements are generated again in Segments whose organization is '2' (C:030380)
GCO: Occursed Data Elements and the associated SQL indicator are generated again in Segments whose organization is '2', even if the DESCR=ALL option has not been indicated in the corresponding Block.

Moreover for a GCP:
The SQL indicator associated with an occursed field of a DB2 Segment is generated again.

Generators - date processing - Correction of various problems (C:030423)
Generators - date processing - Correction of various problems:
1 - For all the operators and condition types related to dates, the working fields can be up to 30 characters long (they are no longer truncated).
Moreover, if the date format is not specified, it is now found in all cases.
2 - 'DC' condition type: the word 'not' is correctly processed, even if it is in lowercase letters.
3 - 'DO' condition type: the 'bound' fields are no longer truncated.

Reminder: the 'bound' fields cannot exceed 24 characters.

Caution: in some cases, the generated code is modified to put the condition on 2 lines.

Erroneous format in the Report Call of Elements of a batch Program (C:030543)
Erroneous format in the Report Call of Elements of a batch Program.
The Data Elements with a signed format (1st character = S) are no longer generated as X(8) in the Report Call of Elements of a Program.

Incorrect generation of segments in T or X (table) use (C:030613)
Incorrect generation of segments in T or X (table) use - (New generation limit for GCP and GCD: a segment can now contain 9999 data elements).
In a table, the common part is now correctly generated before the specific part.

The CO operator (Case Of) generated date breakdown (day, month, year) on the Procedural Code (C:030680)
The CO operator (Case Of) used to generate the date breakdown (day, month, year) on the Procedural Code if the last Data Element of the last Segment processed was a date ...
This has been corrected.

Client/Server system develop.

Comm. monitor and folder manager: the record number in the work file can be higher than 999 (C:030186)
The communication monitor and the folder manager manage records with a number higher than 999.

The options in the -GO screen of a database block do not trouble the generation anymore (C:030190)
The options in the -GO screen of a database block do not trouble the generation anymore.
1. If a program with a '2'-type organization segment had an associated block (specified in the 'EXTERN' field) with at least one option in its -GO screen, the generated program was incomplete (segments of the -CD and specific processing not generated !!):
This has been corrected.

2. For the GCO, GGS and GGC commands, the DESCR=ALL option (-GO of the block) was ignored when it was preceded by an option.
This is also corrected.

The session number is correctly filled in when generating an 'S'-type Screen via the GVC command (C:030337)
When generating an 'S'-type Screen via the GVC command, the field which corresponds to the session number is correctly filled in.

Client/Server system dev. 3.x

Unisys Communication Monitor - Folder Manager with a RDMS database: INCLUDE SQLCA wrongly generated (C:028674)
Unisys 2200 Communication Monitor and Folder Manager with a RDMS database:
The INCLUDE SQLCA clause was wrongly generated in the Communication Monitor and in the Folder Manager. And, in the Folder Manager, the SQLCODE declaration was wrongly missing.
This has been corrected.

Close of the work file conditioned by its effective open (C:030056)
The close of the work file is correctly performed if this file has been opened and if an access error has been detected in the processing continuation.

Data Structure

The 'Y' type is authorized again for Data Structures (C:030402)
The 'Y' type is authorized again for Data Structures.
The retrieval keeps the 'Y' type for Data Structures (it no longer changes it to 'Z').
The 'Y' type (Gip folder) is authorized for Data Structures (DS Definition, UPDT ...).
The Segments whose description type is 6, 7 or 8 are then correctly generated again.

Database Block (DDL)

PF11 branching on a database block description and on a segment (C:030109)
For the database blocks and segments, the PF11 function key allows to branch on the generation elements.

B......GN...: The SQL return code is not displayed after a request for a catalog updating. (C:030383)
B......GN...: The SQL return code is not displayed after a request for a catalog updating.
This has been corrected.

GCB: In a Block generated code, there are no longer quotes in the Segment name. (C:030475)
GCB: In a Block generated code, there are no longer quotes in the Segment name.
In the generated code of a Block, the quotes in the value of the 'record-type Element' are now replaced with blanks, according to the value of the delimiter indicated on the Library Definition.

Dictionary

LXE command: the update timestamp of a Data Element is no longer recognized as a use (C:030202)
LXE command: the update timestamp of a Data Element is no longer recognized as a use.
When a Data Element only has an update timestamp, without any other use, it is displayed in the 'List of unused Data Elements and Properties' (LXE generation/print command).

The error 6157 ('THE ENTITY CODE MUST NOT CONTAIN BLANKS') is changed into a warning (C:030363)
The error 6157 is now changed into a warning and the message is:
'THE ENTITY CODE CONTAINS BLANKS'.

PacDesign Methodologies

VINS: Update of the methodology Meta Entities in inter-library mode (C:030560)
VINS: Update of the methodology Meta Entities in inter-library mode. (for Microfocus or Acucobol environment).
Updating Meta Entities in inter-Library mode is now possible even if these Meta Entities already exist in a lower-level Library.

VINS, installation of methodologies: deletion of the Methodology entities in Libraries. (C:030567)
VINS, installation of methodologies: deletion of the Methodology Meta-Entities in all Libraries.
The installation of Methodologies must be performed in session 1 and in inter-library mode.
At the same time, the Methodologies which already exist in various Libraries are now correctly suppressed.
Moreover, the error 6456C no longer appears upon a VINS installation.

eBusiness Module

Comm. monitor and folder manager: the record number in the work file can be higher than 999 (C:030186)
The communication monitor and the folder manager manage records with a number higher than 999.

Generators

SCM: The number of generation commands processed in the same run is now extended to 9999 (C:030367)
SCM: A crash occurred when the number of generation commands exceeded 1000 in the same run. This number is now extended to 9999.

Generated programs

Correct management of the '.' back to the MCI operator in the batch and online generators (C:028648)
Correct management of the '.' back to the MCI operator for the GCP and GCO generations.

Unisys Communication Monitor - Folder Manager with a RDMS database: INCLUDE SQLCA wrongly generated (C:028674)
Unisys 2200 Communication Monitor and Folder Manager with a RDMS database:
The INCLUDE SQLCA clause was wrongly generated in the Communication Monitor and in the Folder Manager. And, in the Folder Manager, the SQLCODE declaration was wrongly missing.
This has been corrected.

GCP / CASE OF: the values input after the 'IT' are no more truncated (C:030040)
GCP / CASE OF: the values input after the 'IT' are no more truncated.
The IT instruction that follows the CASE OF is now generated on 2 lines in order to avoid the truncation problems.

Close of the work file conditioned by its effective open (C:030056)
The close of the work file is correctly performed if this file has been opened and if an access error has been detected in the processing continuation.

The options in the -GO screen of a database block do not trouble the generation anymore (C:030190)
The options in the -GO screen of a database block do not trouble the generation anymore.
1. If a program with a '2'-type organization segment had an associated block (specified in the 'EXTERN' field) with at least one option in its -GO screen, the generated program was incomplete (segments of the -CD and specific processing not generated !!):
This has been corrected.

2. For the GCO, GGS and GGC commands, the DESCR=ALL option (-GO of the block) was ignored when it was preceded by an option.
This is also corrected.

The session number is correctly filled in when generating an 'S'-type Screen via the GVC command (C:030337)
When generating an 'S'-type Screen via the GVC command, the field which corresponds to the session number is correctly filled in.

C30231 follow-up - Erroneous segment gener. (GCP) if segment select. = common part + specific part (C:030373)
Erroneous segment generation (GCP) if the segment selection contains the common part and the renamed specific part.

The data elements of the common and specific parts were wrongly mixed (first data element of the specific part back to the first data element of the common part, second data element of the specific part back to the second data element of the common part, etc.).
This has been corrected. In the generated Cobol, first appear all the data elements of the common part, followed by all the data elements of the specific part.

GCO: Occursed Data Elements are generated again in Segments whose organization is '2' (C:030380)
GCO: Occursed Data Elements and the associated SQL indicator are generated again in Segments whose organization is '2', even if the DESCR=ALL option has not been indicated in the corresponding Block.

Moreover for a GCP:
The SQL indicator associated with an occursed field of a DB2 Segment is generated again.

Generators - date processing - Correction of various problems (C:030423)
Generators - date processing - Correction of various problems:
1 - For all the operators and condition types related to dates, the working fields can be up to 30 characters long (they are no longer truncated).
Moreover, if the date format is not specified, it is now found in all cases.
2 - 'DC' condition type: the word 'not' is correctly processed, even if it is in lowercase letters.
3 - 'DO' condition type: the 'bound' fields are no longer truncated.

Reminder: the 'bound' fields cannot exceed 24 characters.

Caution: in some cases, the generated code is modified to put the condition on 2 lines.

The quotes of the value of a Segment 'record-type Element' are replaced with blanks (C:030437)
The quotes of the value of a Segment 'record-type Element' are replaced with blanks.
In the generated code of a screen, the quotes of the value of the 'record-type Element' are now replaced with blanks, according to the value of the delimiter indicated on the Library Definition.

GCB: In a Block generated code, there are no longer quotes in the Segment name. (C:030475)
GCB: In a Block generated code, there are no longer quotes in the Segment name.
In the generated code of a Block, the quotes in the value of the 'record-type Element' are now replaced with blanks, according to the value of the delimiter indicated on the Library Definition.

GCO / an initial value is recognized for a numeric protected field (C:030528)
GCO / an initial value is recognized for a numeric protected field.
If an initial value is specified for a numeric protected field ('F' nature), then the loading of this initial value is generated in the F8115 subfunction.

When DATSEP and DATSET are explicitly set, they are no longer overwritten (AD, AD0, AD1, AD2) (C:030537)
When DATSEP and DATSET are explicitly set, they are no longer overwritten (AD, AD0, AD1, AD2).

WARNING ! The date processing function (F9520 for the batch function and F8120 for the other generators) uses a new field for the separator: DATSEW.

In the generation of the AD, AD0, AD1, AD2 operators, the separator is correctly set: with the separator included in the date, if any, or with DATSEP (dates with an E or M format) or DATSET (dates with a G format) otherwise.

Erroneous format in the Report Call of Elements of a batch Program (C:030543)
Erroneous format in the Report Call of Elements of a batch Program.
The Data Elements with a signed format (1st character = S) are no longer generated as X(8) in the Report Call of Elements of a Program.

Incorrect generation of segments in T or X (table) use (C:030613)
Incorrect generation of segments in T or X (table) use - (New generation limit for GCP and GCD: a segment can now contain 9999 data elements).
In a table, the common part is now correctly generated before the specific part.

Dialogue: Some generated lines concerning the UNISYS-A generation were wrong (C:030637)
Dialogue: Some generated lines concerning the UNISYS-A generation were wrong.
An adaptation of some lines containing the character 'à' to be transformed in '@' could also modify the lines structure.
The generated code was erroneous.
This has been corrected.

The CO operator (Case Of) generated date breakdown (day, month, year) on the Procedural Code (C:030680)
The CO operator (Case Of) used to generate the date breakdown (day, month, year) on the Procedural Code if the last Data Element of the last Segment processed was a date ...
This has been corrected.

Database management

The reorganization procedure (REOR) filters erroneous data (C:030522)
If the session number of a record is greater than the current session number, this record is not taken into account.
It will appear in the report of step PTU200, with the following error message: INVALID SESSION.

Meta-entities

PAF: a $ttDxx with an entity linked to a $/Ytt equal to the $/YttDEF one is now correct (C:027696)
A $/YttDxx extraction with a $/Ytt type linked entity equal and with the same link in the $/YttDEF is now correct : before correction, the value of the linked field in the description was the one in the definition.
Corrected.

UTM2: the label of the old relation is retrieved in case of transformation into new relation (C:030080)
UTM2: If an old relation is changed into a new relation, its label is kept.

User entities: warning if areas cannot be displayed in online mode (C:030082)
When the description of user entities is displayed in online mode, if the remaining place on the line is not enough to completely display the following data, a warning is displayed.
--> The AE file must be retrieved.

EXPU: Search of entities to be purged on a user entity call type (C:030087)
PACX-EXPU: Search of entities to be purged on a user entity call type.
According to the other Pacbase entities, it is now possible to logically or physically purge user entities (excluding random data).
The search is performed by specifying '$' or 'Y' in column '7' of the user input and the meta entity call type in position '14'.
If the entity type is not specified, the search is performed on all entity types of the database.

UTM1: limitation of the -CR extraction to the processed relation (C:030111)
UTM1/UTM2: limitation of the -CR extraction to the processed relation.
When an entity called, for a same line number, different relations in different sessions, UTM1 wrongly extracted, for each relation, all the records (-CR) corresponding to this line number, including data that concerned other relation codes.
The extraction is now limited to the processes relation.

LOCKS: a selection on both a $/Ytt entity type and the entity code is now possible (C:030264)
LOCKS: a selection on both a $/Ytt entity type and the entity code is now possible even if this entity is just after another user entity in the LL screen for the same user.

No more improper repetition of fields in a user entity description (C:030316)
No more improper repetition of fields in the extraction of a user entity description after an access by PAF to the definition of this user entity.

Meta Entity: call of a Data Element defined more than once in the network if its format is the same (C:030347)
The description of a Meta Entity can call a Data Element defined more than once in the Libraries network if its format is always identical in these various Libraries.
In this case, the 8488E error message will no longer be displayed.

After PC25 retrieval, the descriptions of Meta Entities can be aligned (C:030375)
After the retrieval, the description of a Meta Entity, defined in various Libraries, can be aligned.
A Meta Entity will be chosen as the reference (master).
The same Meta Entity (target), which exists in another network, can be modified in order to be the image of the master Meta Entity.
The internal identifiers of the Data Elements which are common to the master and the target will be aligned.
Only modifications will be performed: if the target description is more complete, it will remain as such.
If Data Elements of the master Meta Entity are not called in the target Meta Entity, the descriptions of the target will not be completed.
The User Entities of the modified target Meta Entity will also be modified.
You must perform the following operations:
- Save the Database
- Extract the master Meta Entity via EXTR with the CPSN format
- Modify the target Meta Entity and its UE via Vins.
In the VINS user input, you must indicate:
. the Library of the target Meta Entity
. 'F' in column 33

Assignment of Text lines: The User Entities whose identifier is 6 char. long max. may not exist (C:030399)
Assigning Text lines to a User Entity which does not exist is now possible if the identifier of this User Entity is 6 characters long maximum.

Correct deletion of an old UE which contains a Data Element (x(6) format) linked to a Segment (C:030408)
An old UE which contains a Data Element (x(6) format) linked to a Segment via a Relation can now be deleted without any problem.
This change also applies to the Data Elements linked to Reports or Data Structures.

On-Line System Development

Correct management of the '.' back to the MCI operator in the batch and online generators (C:028648)
Correct management of the '.' back to the MCI operator for the GCP and GCO generations.

The options in the -GO screen of a database block do not trouble the generation anymore (C:030190)
The options in the -GO screen of a database block do not trouble the generation anymore.
1. If a program with a '2'-type organization segment had an associated block (specified in the 'EXTERN' field) with at least one option in its -GO screen, the generated program was incomplete (segments of the -CD and specific processing not generated !!):
This has been corrected.

2. For the GCO, GGS and GGC commands, the DESCR=ALL option (-GO of the block) was ignored when it was preceded by an option.
This is also corrected.

GCO: Occursed Data Elements are generated again in Segments whose organization is '2' (C:030380)
GCO: Occursed Data Elements and the associated SQL indicator are generated again in Segments whose organization is '2', even if the DESCR=ALL option has not been indicated in the corresponding Block.

Moreover for a GCP:
The SQL indicator associated with an occursed field of a DB2 Segment is generated again.

Generators - date processing - Correction of various problems (C:030423)
Generators - date processing - Correction of various problems:
1 - For all the operators and condition types related to dates, the working fields can be up to 30 characters long (they are no longer truncated).
Moreover, if the date format is not specified, it is now found in all cases.
2 - 'DC' condition type: the word 'not' is correctly processed, even if it is in lowercase letters.
3 - 'DO' condition type: the 'bound' fields are no longer truncated.

Reminder: the 'bound' fields cannot exceed 24 characters.

Caution: in some cases, the generated code is modified to put the condition on 2 lines.

The quotes of the value of a Segment 'record-type Element' are replaced with blanks (C:030437)
The quotes of the value of a Segment 'record-type Element' are replaced with blanks.
In the generated code of a screen, the quotes of the value of the 'record-type Element' are now replaced with blanks, according to the value of the delimiter indicated on the Library Definition.

GCO / an initial value is recognized for a numeric protected field (C:030528)
GCO / an initial value is recognized for a numeric protected field.
If an initial value is specified for a numeric protected field ('F' nature), then the loading of this initial value is generated in the F8115 subfunction.

Dialogue: Some generated lines concerning the UNISYS-A generation were wrong (C:030637)
Dialogue: Some generated lines concerning the UNISYS-A generation were wrong.
An adaptation of some lines containing the character 'à' to be transformed in '@' could also modify the lines structure.
The generated code was erroneous.
This has been corrected.

Pacbase Access Facility

PAF: a $ttDxx with an entity linked to a $/Ytt equal to the $/YttDEF one is now correct (C:027696)
A $/YttDxx extraction with a $/Ytt type linked entity equal and with the same link in the $/YttDEF is now correct : before correction, the value of the linked field in the description was the one in the definition.
Corrected.

The PAF preprocess will now generate in multi-screen variant option ('C') an EXEC CICS LINK (C:030210)
The PAF preprocess will now generate in multi-screen variant option ('C') an EXEC CICS LINK instead off a CALL order.

SCRDEF cursor: the before/after cards of a dialogue are now correctly extraction in 'I' view (C:030255)
SCRDEF cursor: the before/after cards of a dialogue are now correctly extracted in 'I' view on the definition screen.

LOCKS: a selection on both a $/Ytt entity type and the entity code is now possible (C:030264)
LOCKS: a selection on both a $/Ytt entity type and the entity code is now possible even if this entity is just after another user entity in the LL screen for the same user.

DSTDEF: the last character of the keywords field in X(55) is no more truncated (C:030269)
DSTDEF table: the last character of the keywords field in X(55) is no more truncated.

DLGCMP: the selection on the dialogue code (with inf. and sup. boundaries, or equality) is correct (C:030288)
DLGCMP: the selection on the dialogue code (with inferior and superior boundaries, or equality) is now correct.

The errors found in the PAF pre-processor no longer cause an ABEND (C:030312)
The errors found in the PAF pre-processor no longer cause an ABEND.

No more improper repetition of fields in a user entity description (C:030316)
No more improper repetition of fields in the extraction of a user entity description after an access by PAF to the definition of this user entity.

SEGXCRLCAL: a selection on the type and code of the linked entity now works fine (C:030350)
SEGXCRLCAL: a selection on the type and code of the linked entity now works fine.

The format of the linked entity code in all the xxxCAL/CAE tables is now X(30) (C:030352)
The length of the area corresponding to the CENT column code could be 6 or 30.
Now, the CENT column code has a 30-characters length for all the xxxCAL/CAE tables.

SEGDEL with an indicator equal to 'M' (multiple key) -> the Data Element level is now correct (C:030385)
SEGDEL with an indicator equal to 'M' (multiple key) -> the missing information (Data Element level and pictures) is now correctly extracted.

An extraction about 'OLD' user entities will no more look for the internal code (C:030572)
As the old user entities always have a 6-characters code, it is useless to look for the internal code (it is the same as the long code).

Batch Procedures

UTM2: a step to check the ME file issued from UTM1 has been added (C:029926)
UTM2: a step to check the ME file issued from UTM1 has been added.
The ME file issued from the UTM1 procedure contains the list of relation calls. Each relation must be linked to only one entity type.
To guarantee the validity of this file, a control program (ptume3) is added in the UTM2 procedure.
If several entity types are linked to a same relation, a display is sent requesting the correction and the re-execution of UTM2.

EXPU: Search of entities to be purged on a user entity call type (C:030087)
PACX-EXPU: Search of entities to be purged on a user entity call type.
According to the other Pacbase entities, it is now possible to logically or physically purge user entities (excluding random data).
The search is performed by specifying '$' or 'Y' in column '7' of the user input and the meta entity call type in position '14'.
If the entity type is not specified, the search is performed on all entity types of the database.

UPDT: when a definition with a keyword is deleted, the timestamp is deleted (C:030099)
UPDT: when a definition with a keyword was deleted, the timestamp was wrongly kept.
It is now deleted.

REOR procedure: the output report containing the purged data is complete (C:030119)
If the purge of non existing data is requested, these are printed in the list of purged data with the message 'NOT FOUND'.

EXLI: if several extractions are requested, the context is correct for the child data elements (C:030168)
EXLI: is several extractions are requested, the context is correct for the child data elements.
If EXLI contained several input cards, the Pacbase context, used to search information on the parent data element, could be erroneous.
This has been corrected.

Optimization of the PJ25 and UV25 retrieval procedures (C:030209)
Optimization of the 2.5 -> 3.5 retrieval procedures:
- of the PJ file (BVPPJ25 procedure) by limiting the accesses to the AE file
- of the UV file (BVPUV25 procedure) by limiting the accesses to the AE file and deletion of the loop if the maxi key is missing in the 2.5 UV file.

UPDT-PAC7IE: The vertical and horizontal characters of the Library are recognized (C:030240)
The PAC7IE report of UPDT now recognizes the vertical and horizontal characters indicated on the Library Definition.
The PAC7ID report of GPRT now includes the labels PAGE, ANOMALIES and the bottom frame in the list of commands.

UPDT: Incomplete transactions on keywords could impair the update of timestamps (C:030248)
UPDT: Incomplete transactions on keywords could impair the update of timestamps.
If a header transaction for the update of an entity's keywords was not followed by the transaction which contained the keywords, it was ignored.
This could prevent the entity timestamp from being updated.
This is now corrected.

GPRT: The uses of an Input Aid are no longer truncated in the DCI command (C:030263)
GPRT: The uses of an Input Aid are no longer truncated in the DCI command.
These fields, which are 75 characters long, were truncated to 71 characters.
This has been corrected.

Meta Entity: call of a Data Element defined more than once in the network if its format is the same (C:030347)
The description of a Meta Entity can call a Data Element defined more than once in the Libraries network if its format is always identical in these various Libraries.
In this case, the 8488E error message will no longer be displayed.

UPDT: Management of update transactions on Data Elements (C:030359)
Now updating only one of the three formats of a Data Element is possible via the UPDT procedure.
In the identification line, the user must not indicate an 'N' in column 67.

UTM2 will create the new Relation in the Library in which a Meta Entity uses it (C:030360)
UTM2 will create the new Relation in the Library in which a Meta Entity uses it.

The error 6157 ('THE ENTITY CODE MUST NOT CONTAIN BLANKS') is changed into a warning (C:030363)
The error 6157 is now changed into a warning and the message is:
'THE ENTITY CODE CONTAINS BLANKS'.

The reorganization procedure (REOR) filters erroneous data (C:030522)
If the session number of a record is greater than the current session number, this record is not taken into account.
It will appear in the report of step PTU200, with the following error message: INVALID SESSION.

Partially updating an Input Aid call used to wrongly reset the other fields to blank. (C:030558)
In batch mode, updating some of the fields of an Input Aid call used to reset to blank all the other fields of this Input Aid.
This has been corrected.

VINS: Update of the methodology Meta Entities in inter-library mode (C:030560)
VINS: Update of the methodology Meta Entities in inter-library mode. (for Microfocus or Acucobol environment).
Updating Meta Entities in inter-Library mode is now possible even if these Meta Entities already exist in a lower-level Library.

The name of the temporary directory for the Cobol sort can be modified at procedure launch (C:030650)
The name of the temporary directory for the Cobol sort can be modified at procedure launch.
The modification of the temporary files directory name ($PACTMP) requested with the '-t' parameter at the procedure execution also impacts the environment variable used for the name of the directory assigned to the Cobol sort (TMPDIR or SORT_DIR) if it has not been specified.

Retrieve

UTM2: a step to check the ME file issued from UTM1 has been added (C:029926)
UTM2: a step to check the ME file issued from UTM1 has been added.
The ME file issued from the UTM1 procedure contains the list of relation calls. Each relation must be linked to only one entity type.
To guarantee the validity of this file, a control program (ptume3) is added in the UTM2 procedure.
If several entity types are linked to a same relation, a display is sent requesting the correction and the re-execution of UTM2.

MB25: the insignificant '&' are taken into account in the comments retrieval (C:030047)
MB25: the insignificant '&' are taken into account in the comment retrieval.
The 'V3' comment lines were incorrectly formatted and the type of line was '&'.
This has been corrected.

UTM2: the label of the old relation is retrieved in case of transformation into new relation (C:030080)
UTM2: If an old relation is changed into a new relation, its label is kept.

UTM1: limitation of the -CR extraction to the processed relation (C:030111)
UTM1/UTM2: limitation of the -CR extraction to the processed relation.
When an entity called, for a same line number, different relations in different sessions, UTM1 wrongly extracted, for each relation, all the records (-CR) corresponding to this line number, including data that concerned other relation codes.
The extraction is now limited to the processes relation.

Optimization of the PJ25 and UV25 retrieval procedures (C:030209)
Optimization of the 2.5 -> 3.5 retrieval procedures:
- of the PJ file (BVPPJ25 procedure) by limiting the accesses to the AE file
- of the UV file (BVPUV25 procedure) by limiting the accesses to the AE file and deletion of the loop if the maxi key is missing in the 2.5 UV file.

PG25: The addition of before/after cards on the GCD command description is taken into account (C:030214)
PG25: The addition of before/after cards on the description of the GCD command is taken into account.
The before/after cards fields of a GCD command issued from the 2.5 version are set to blank.

PC25: Reinitialization of the Input Aid type
(C:030335)

PC25: Reinitialization of the Input Aid type.
The Input Aid type is found on the description. It is reinitialized each time a new Input Aid is processed.
When this type was not specified (set to blank) on the description and when the first description line was a comment line, the Input Aid type was that of the previous Input Aid.
This has been corrected.

UTM2 will create the new Relation in the Library in which a Meta Entity uses it (C:030360)
UTM2 will create the new Relation in the Library in which a Meta Entity uses it.

After PC25 retrieval, the descriptions of Meta Entities can be aligned (C:030375)
After the retrieval, the description of a Meta Entity, defined in various Libraries, can be aligned.
A Meta Entity will be chosen as the reference (master).
The same Meta Entity (target), which exists in another network, can be modified in order to be the image of the master Meta Entity.
The internal identifiers of the Data Elements which are common to the master and the target will be aligned.
Only modifications will be performed: if the target description is more complete, it will remain as such.
If Data Elements of the master Meta Entity are not called in the target Meta Entity, the descriptions of the target will not be completed.
The User Entities of the modified target Meta Entity will also be modified.
You must perform the following operations:
- Save the Database
- Extract the master Meta Entity via EXTR with the CPSN format
- Modify the target Meta Entity and its UE via Vins.
In the VINS user input, you must indicate:
. the Library of the target Meta Entity
. 'F' in column 33

UTM2: the relations are now created in the H session which is the closest to its use in entity (C:030387)
UTM2 will create the new Relation in the same session as that of its use in an entity (c30360 follow-up).

Software Config. Management

SCM: The number of generation commands processed in the same run is now extended to 9999 (C:030367)
SCM: A crash occurred when the number of generation commands exceeded 1000 in the same run. This number is now extended to 9999.

PACBASE SIGAGIP Interface

The 'Y' type is authorized again for Data Structures (C:030402)
The 'Y' type is authorized again for Data Structures.
The retrieval keeps the 'Y' type for Data Structures (it no longer changes it to 'Z').
The 'Y' type (Gip folder) is authorized for Data Structures (DS Definition, UPDT ...).
The Segments whose description type is 6, 7 or 8 are then correctly generated again.

Text

CH: T......D: positioning marks on I- and J-type lines (C:030390)
In character mode, the I- and J-type lines which are used to assign text lines to the documentation of entities include positioning marks for entering the entity codes to which text lines will be assigned.

Assignment of Text lines: The User Entities whose identifier is 6 char. long max. may not exist (C:030399)
Assigning Text lines to a User Entity which does not exist is now possible if the identifier of this User Entity is 6 characters long maximum.

Miscellaneous : Online

User entities: warning if areas cannot be displayed in online mode (C:030082)
When the description of user entities is displayed in online mode, if the remaining place on the line is not enough to completely display the following data, a warning is displayed.
--> The AE file must be retrieved.

PF11 branching on a database block description and on a segment (C:030109)
For the database blocks and segments, the PF11 function key allows to branch on the generation elements.

Meta Entity: call of a Data Element defined more than once in the network if its format is the same (C:030347)
The description of a Meta Entity can call a Data Element defined more than once in the Libraries network if its format is always identical in these various Libraries.
In this case, the 8488E error message will no longer be displayed.

B......GN...: The SQL return code is not displayed after a request for a catalog updating. (C:030383)
B......GN...: The SQL return code is not displayed after a request for a catalog updating.
This has been corrected.

CH: T......D: positioning marks on I- and J-type lines (C:030390)
In character mode, the I- and J-type lines which are used to assign text lines to the documentation of entities include positioning marks for entering the entity codes to which text lines will be assigned.

Correct deletion of an old UE which contains a Data Element (x(6) format) linked to a Segment (C:030408)
An old UE which contains a Data Element (x(6) format) linked to a Segment via a Relation can now be deleted without any problem.
This change also applies to the Data Elements linked to Reports or Data Structures.

For Programs written in lines 8, the long conditions are managed correctly (C:030426)
For Programs written in lines 8, the long conditions are managed correctly.
In the lines '8' where the condition is written on more than 32 characters, the 3 characters which are not displayed are not reset to blank.

Report layout: the modification of label number or jump code is correctly journalized (C:030541)
Report layout: the modification of label number or jump code is correctly journalized.
If a line is modified at label number level or jump code level but without modification in the content of the line and if the visualization window begins with a value different from 1, 67, 133 and 199, the journalization transaction is associated with the first part of the label.

Update of long data in two contexts
(C:030665)

Update of long data in two contexts

'Long' data is data which cannot fit into a physical record of the AR file.
This applies to:
- User Entities (Definition or Description)
- All the -Gx type Descriptions which include a call to an Input Aid
- The description of Report labels

The creation of this data in a session no longer impacts the images of this data in another context.

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

VisualAge Pacbase
VisualAge Pacbase Server

Software version:

3.5

Operating system(s):

AIX, IRIX, Linux, Solaris, Unisys A-Series

Reference #:

1258724

Modified date:

2014-06-04

Translate my page

Machine Translation

Content navigation