G8 - Organise Pointers

Datafile Software

G8 – Organise Pointers

This is similar to option type O-Organise Pointers but may be personalised a lot more and is capable of re-organising pointers on files other than the main master file in your current ProFiler application.

Master Database Number

Specify the file number within the application list of files that is the master file. This is usually ‘1’, although as mentioned previously this global update routine would allow the ability to organise pointers for files other than the ‘current’ master file for the application.

Detail Database Number

Specify the file number for the detail database.

Enter Own Datafile Item Specification

If organising the pointers against the application master file then you have probably set the pointers within the Data File Profiles of the application to this detail file in which case you can leave this options blank to use these settings.Alternatively, if using the update to organise pointers for another file set this option to allow entry of the pointer link data items.

Master File: First

Master File: Last

Master File: Total

Master File: Count

Master File: Ent Tot

These inputs ask for data items on the master file. ‘First’ and ‘Last’ refer to the first and last record numbers for details associated with the master record – item type is usually Y(6). ‘Total’ refers to the accumulation value from the detail file item specified as ‘Value’ and is usually a K or L-type. ‘Count’ is a Y(6) type item that counts the number of detail records currently against the master, whilst ‘Ent Tot’ (an N-type field) is the current highest entry added – the difference being that the ‘Count’ doesn’t include deleted records whereas the ‘Ent Tot’ would.

Detail: Next

Detail: Prev

Detail: Value

Detail: Code

Detail: RecNo

Detail: Ent No

These inputs ask for the data items on the detail file. ‘Next’ and ‘Prev’ refer to the record numbers for the next and previous detail record associated with the master record – item type is usually Y(6). The ‘Prev’ value is optional and is only required if require LIFO print/display for a master/detail screen or report, most application databases do not have a previous pointer. The ‘Value’ item refers to the item to be accumulated to the master record ‘Total’ item and is usually a K or L-type. The ‘Code’ is the detail item that contains the matching prime-index value of the master file. The ‘RecNo’ contains the record number for the associate master record and is usually a Y(6) type and the ‘EntNo’ contains the entry number for the current detail record and is an N-type field.

Fast Run, Only if No Master Record Number?

Your ProFiler application may add records to the detail file via data interchange or extract procedures which would not update the pointer chain to the master record. As the pointer audit may take some time on large detail files setting this option allows you to reduce the time taken by only updating the pointers for the new records added – those without a master record number. Set as required.

Re-Organise in User Defined Sequence

The re-organise arranges the details in the order they were added to the file. Setting this option allows you to organise in another order – perhaps a date for example. Note that this does not change the order within the database but instead structures the pointers so that a master/detail screen or print lists the records in the order specified. Set as required.

Sort Only (Do Not Re-Index)

If set to re-organise then again this can take some time as it rebuilds the full pointer relationship.Setting this option assumes the existing pointer relation is ‘correct’ but need to be re-organised only – i.e. all the details are associated with the appropriate master record but you wish to change the order of display. If set then a third screen allows additional parameters later.

Item (1/2/3)

Size

Ascend/Descend

If set to re-organise in a user-defined sequence these options allow you to define the sequence in which the details are organised. Select the data items as required, the size defaults to the item size of the data item but you can reduce this if required, then selected whether the items are to be sorted in ascending or descending order.

Ask for Specific Master Record?

Master Items to Display

Only applicable if set to ‘Sort Only (do not re-index)’ above. At run-time if enabled you will be asked to select a specific master record for which to sort the detail pointers. The Items to display should be set to allow you to ensure you have selected the correct record.

The next section allows you to set and use record number ‘slots’ within the update though it would be unusual to use this option on an organise routine – generally you wouldn’t exclude records. These ‘slots’ are counters stored against the database and can be used to increase the speed of an update, so historical records aren’t reprocessed and to speed subsequent follow-on procedures.

Each database has 10 slots that can be used – but note that the standard applications will be using these slot numbers also (the sales transaction file for example uses slots 1-8 as part of general processing) so care should be taken when using this option on standard application databases.

Store Highest Record Number Updated in Which Slot (1-10)

Set the slot number to be updated with the highest record processed. Once saved this can be used in the next prompt as the starting point for the next update run.

Start from Record Number in which Slot Number (1-10)

Set the slot number for which to start processing the update from (in fact it starts from this value plus ‘1’ to start on the next record). It is usual to set both this and the previous parameter to the same slot number where no subsequent procedures are to use the same set of records.

Store First Record Processed in Slot Number (1-10)

When running a series of procedures that are going to be reporting/updating the same set of data it can speed subsequent processes if you record the first record processed on the update into the slot numbers. This can then be used as the starting point in subsequent procedures.

Runtime Prompts

This option allows three lines of text that can be displayed to the operator when the global update option is selected. This text could include instructions for any follow-on procedures such as pointer audits that may be required.

Specify Search Criteria

Allow Run Time Changes to Search

Save Any Changes

Set as appropriate to pre-define any search criteria (records are excluded from the pointer audit that do not match the criteria), whether run-time changes to the criteria are allowed, and whether or not to save these changes for the next run.

Respond ‘No’ to save the update definition, ‘Yes’ to go back to the data items to amend the definition or <Esc> to abandon without saving.