Mapping Edit MQMX

This screen is the key to the Mapping construction set; it is the centre of the Mapping development environment and you will return to it repeatedly. You can invoke any of the other screens and processes from here. Use this screen to create a new Mapping, amend a Mapping, compile a Mapping and submit a Mapping for execution.

There are two ways to create a new Mapping: from nothing, or from a copy of an existing Mapping. To create a new Mapping from nothing, start this screen with the Insert action, enter an identifier and description, then Update. (Otherwise, use the screen Mapping - Copy MQMO.)

Note that when you Insert a new Mapping, you can only create the Mapping header record, with an identifier and a description; you cannot add any components until the header has been stored using Update.

Add new components to a Mapping using the Insert action; revise or alter existing components using the Edit Amend action. Each component type is handled by a different screen and they are all available from this one.

The first format of this screen lists the components of the current Mapping; the second format shows information about the Mapping such as the last time it was updated and the last time it was compiled.

When a new component is added to a Mapping using the Insert action, it appears at the beginning of the list and all other components move down accordingly. If the special action Insert Here is used, then a new component can be added at any point in the list, with other components moving down as required. If you use an Insert action more than once without Updating, then the new components will be put in alphabetic order by name within their component types; this is because of the way QED keeps track of the components. The order of the components can be changed at any time by use of the normal editing action M (for Move) on the line of the component to be moved and F (for Following) or P (for Preceding) on the line of the component which the moved component is to follow or precede. See Common Features for a complete list of Editing Actions.

A Mapping can have any number of components, but it must have one (and only one) level-type component called Main. Although components can be added to a Mapping in any order, we recommend that a level called Main is always created first, even if it does not contain any MDL code, so that this basic system requirement is satisfied. All other components are optional; their use depends on the purpose for which the Mapping is being built. Depending on that purpose, it can make sense to set up the report component first and then develop the processing to go with it, or it can seem easier the other way round; it does not matter.

Components can be deleted from a Mapping by selecting them then using the Edit Purge action. For each selected component, the appropriate screen is displayed and you can choose Update to confirm the deletion, or Exit to abandon the deletion and keep the component.

As you develop a Mapping, you can do syntax checks on the various components; a Syntax Compile on this screen performs the same service for the entire Mapping and, if successful, will guarantee a successful Compile.

When developing or amending Mappings, there are security aspects to consider. If Mapping authorisation is in use for the company to which the Mapping belongs, then changes to an authorised Mapping automatically make it unauthorised. Access to Mappings owned by other users can be restricted, so preventing you from amending them. You may not be allowed access to all the data your Mapping is designed to extract, in which case your Mapping cannot extract any data. A particular Mapping may also be disabled (its use can be prohibited). See QED System Adminstration for more information on Security.

MQMX Fields

Type

The type of component - report, level, parameter and so on.

Name

The identifier of the component, up to 18 alphanumeric characters.

Description

The description of the component, up to 40 characters.

User

ID and name of the user who owns the Mapping. Initially, this is the user who creates the Mapping, but the ID can be changed (ownership can be reassigned). Depending on the way security groups have been set up, you may not be able to amend Mappings owned by other users.

Authorised

This field is used to authorise amendments to a Mapping and is relevant only if authorisation is required according to the Company Controls. It can contain only 'Y' or blank. If authorisation is in use, you may not be able to amend this field and you may not be able to compile the Mapping even though changes you make are stored when you Update. See QED System Admininstration Overview for more information.

Program to Generate

If this Mapping is the source for a program, this field contains the name of the program. The program indicated by this field cannot be requested using the normal QED submission routines; it is usually part of an e5 process. If this field is used, then the fields System Reference and Plan Reference are blank. This field is usually blank and you will not be able to amend it.

Last Component Updated

These are system-maintained information fields. They show when and by whom the last changes were made to the Mapping.

System Reference / Plan Reference

These are system-maintained fields which indicate the unique identifiers assigned to the compiled version of the Mapping. These identifiers are constructed from elements defined in the Company Controls.

Compiled

These are system-maintained fields which show the last time the Mapping was successfully compiled and the ID of the user who initiated the compilation.

Screen Specific Actions

Action	Description
Compile & Go	This action causes the current Mapping to be compiled. If successfully compiled, the compiled Mapping is then executed immediately, as an ad hoc request. This is equivalent to manually making a submission after using the Compile action.
Compile Compile	This causes the current Mapping to be compiled. If the Mapping is successful, an executable load module is created. Once this module exists, the Mapping can be included in any ad hoc or scheduled submission. See Compiling a Mapping for more information.
Go Requests	This action transfers you to Request - List MAOA. This builds and displays a list of requests which include the current Mapping.
Insert ...	These actions create a new component in the Mapping and transfer you to the appropriate screen for you to enter the component definitions (MDL statements, report layouts, or whatever). The new component is inserted at the top of the list.
Insert ... Here	These actions create new components and transfer to the appropriate screens, as described above; however, the new component is inserted into the list at the point indicated by the tag (a slash character /) in the Act field. This enables you to group similar components together in the list, regardless of the order they are actually created in.(The sequence in the list has no significance; this facility is provided simply for your convenience.)
Mapping Search	This action transfers you to Mapping Search MQMC. This allows Mapping wide free format text searches.
Mapping Compiles	This action transfers you to Mapping Compiles - List MQND. This builds and displays a list of Mapping compilations.
Mapping Runs	This action transfers you to Mapping Runs - List MQNA. This builds and displays a list of Mapping runs.
Submit Submit	This action creates an immediate, ad hoc request for the running of the Mapping. (The last compiled version of the Mapping is used.) Parameters - Amend MQRA is displayed, for the entry of run time parameters. Confirmation of the submit action is requested before the Mapping is passed for execution. See Running a Mapping for more detail.
Syntax Compile	This performs a full syntax check for the entire Mapping. A compilation listing is produced, which gives more information than a Syntax Check on an individual component. A successful Syntax Compile guarantees that a Mapping can be sucessfully compiled into an executable load module.
View ...	These actions display the contents of documents produced for the current Mapping. View Compile specifically shows the report resulting from the last compilation of the current Mapping, including the full MDL listing. View Documents builds a list of all documents for the Mapping, including compilation reports and processing reports as well as output generated by the Mapping itself.

If not described in this topic, click on a field and press F1 to view help. See Common Fields for more information.

Fast prompt allows you to quickly view a list of options for certain fields.

NOTE Field visibility can be defined by your System Administrator, so not all fields documented may be shown.

See Using the Command Line on opening the screen without going through the menu.