Print Fix (OMQPRTFI) - Help

Print Fix (OMQPRTFI)

The Print Fix command enables you to obtain a printed report of the fix database. You can select fix numbers on numerous selections, making this an extremely powerful command.

The reports also provide some basic time calculations.

Action code (ACTC)

Specify the action code to be used. The possible values are:

*PRINT: Start printing the fix database using these command specifications.

*CLOSE: Use this action code to close the fix database and to perform the last record processing. This option enables you to keep the interface to the object database open until you explicitly close it. This will make the interface; faster.

Application (APPL)

Specify the application code to be used. The possible values are:

*ALL: Do not use the application code as a selection field. All values are valid.

application-code: Specify the application code.

Fix Number (FIX)

Specify the fix number to be used. The possible values are:

*ALL: Do not use the fix number as a selection field. All values are valid.

fix-number: Specify the fix number.

Fix status (FIXS)

Specify the fix status to be used. The possible values are:

*ALL: Do not use the fix status as a selection field. All values are valid.

*OPEN: Select only fixes currently being worked on.

*COMPLETE: Select only completed fixes.

application-code: Specify the application code.

Ratification status (RATS)

Specify the ratification status to be used. The possible values are:

*ALL: Do not use the ratification status as a selection field. All values are valid.

*OPEN: Select only fixes which have ratifications pending. This will show all fixes which still have to be ratified.

*COMPLETE: Select only fixes which are ratified by members of all connected ratification groups.

*REJECTED: Select only fixes of which one of the members of the ratification group rejected the fix.

Fix type (FIXT)

Specify the fix type to be used. The possible values are:

*ALL: Do not use the fix type as a selection field. All values are valid.

fix-type: Specify the fix type.

Release (RLS)

Specify the release to be used. The possible values are:

*ALL: Do not use the release as a selection field. All values are valid.

release-number: Specify the release number.

Development exit count from (DEFR)

Specify the development exit count lower limits to be used. The possible values are:

*ALL: Do not use the development exit count lower limits as a selection field. All values are valid.

number: Specify the lower limits of the development exit count.

Development exit count until (DETO)

Specify the upper limits of the development exit count to be used. The possible values are:

*ALL: Do not use the upper limits of the development exit count as a selection field. All values are valid.

number: Specify the upper limits of the development exit count.

Reason code (REAC)

Specify the reason code to be used. The possible values are:

*ALL: Do not use the reason code as a selection field. All values are valid.

release-number: Specify the reason code.

Priority (PRIN)

Specify the priority code to be used. The possible values are:

*ALL: Do not use the priority code as a selection field. All values are valid.

priority: Specify the priority code.

Programmer (PGMR)

Specify the programmer to be used. The possible values are:

*ALL: Do not use the programmer as a selection field. All values are valid.

programmer-id: Specify the programmer id.

Expected vs realized start date (SDCO)

Specify the relationships between the expected and the realized start date. The possible values are:

*ALL: Do not use the relationship between the expected and realized dates as a selection field. All values are valid.

*LT: Specify that all fixes are selected which were realized in the expected time frame.

*GT: Specify that all fixes are selected which were not realized in the expected time frame (overdue).

Expected start date from (ESFR)

Specify the expected start date lower limits to be used. The possible values are:

*ALL: Do not use the lower limits of the expected start date as a selection field. All values are valid.

date: Specify the expected start dates lower limits.

Expected start date until (ESTO)

Specify the expected start date upper limits to be used. The possible values are:

*ALL: Do not use the upper limits of the expected start date as a selection field. All values are valid.

date: Specify the expected start dates upper limits.

Realized start date from (RSFR)

Specify the realized start date lower limits to be used. The possible values are:

*ALL: Do not use the lower limits of the realized start date as a selection field. All values are valid.

date: Specify the realized start dates lower limits.

Realized start date until (RSTO)

Specify the realized start date upper limits to be used. The possible values are:

*ALL: Do not use the upper limits of the realized start date as a selection field. All values are valid.

date: Specify the realized start dates upper limits.

Expected vs realized completion date (CDCO)

Specify the relationship between the expected and the realized completion date. The possible values are:

*ALL: Do not use the relationship between the expected and realized dates as a selection field. All values are valid.

*LT: Specify that all fixes are selected which were realized in the expected time frame.

*GT: Specify that all fixes are selected which were not realized in the expected time frame (overdue).

Expected completion date from (ECFR)

Specify the expected completion date lower limits to be used. The possible values are:

*ALL: Do not use the lower limits of the expected completion date as a selection field. All values are valid.

date: Specify the expected completion dates lower limits.

Expected completion date until (ECTO)

Specify the expected completion date upper limits to be used. The possible values are:

*ALL: Do not use the upper limits of the expected completion date as a selection field. All values are valid.

date: Specify the expected completion date upper limits.

Realized completion date from (RCFR)

Specify the realized completion date lower limits to be used. The possible values are:

*ALL: Do not use the lower limits of the realized completion date as a selection field. All values are valid.

date: Specify the realized completion dates lower limits.

Realized completion until (RCTO)

Specify the realized completion date upper limits to be used. The possible values are:

*ALL: Do not use the upper limits of the realized completion date as a selection field. All values are valid.

date: Specify the realized completion date upper limits.

Expected vs realized development date (DDCO)

Specify the relationship between the expected and the realized development end dates. The possible values are:

*ALL: Do not use the relationship between the expected and realized dates as a selection field. All values are valid.

*LT: Specify that all fixes are selected which were realized in the expected time frame.

*GT: Specify that all fixes are selected which were not realized in the expected time frame (overdue).

Expected development end date from (EDFR)

Specify the expected development end date lower limits to be used. The possible values are:

*ALL: Do not use the lower limits of the expected development end date as a selection field. All values are valid.

date: Specify the expected development end dates a lower limit.

Expected development end date until (EDTO) - Help

Specify the expected development end date upper limits to be used. The possible values are:

*ALL: Do not use the upper limits of the expected development end date as a selection field. All values are valid.

date: Specify the expected development end date lower limits.

Realized development end date from (RDFR)

Specify the realized development end date lower limits to be used. The possible values are:

*ALL: Do not use the lower limits of the realized development end date as a selection field. All values are valid.

date: Specify the realized development end date as lower limits.

Realized development end date until (RDTO)

Specify the realized development end date upper limits to be used. The possible values are:

*ALL: Do not use the lower limits of the realized development end date as a selection field. All values are valid.

date: Specify the realized development end date lower limits.

Expected vs realized number of hours (NHOU)

Specify the relationship between the expected and the realized number of hours. The possible values are:

*ALL: Do not use the relationship between the expected and realized hours as a selection field. All values are valid.

*LT: Specify that all fixes are selected which were realized in the expected time frame.

*GT: Specify that all fixes are selected which were not realized within the expected time frame (overdue).

Expected number of hours from (EPFR)

Specify the expected number of hours lower limits to be used. The possible values are:

*ALL: Do not use the lower limits of the expected number of hours as a selection field. All values are valid.

date: Specify the expected number of hours lower limits.

Expected number of hours until (EPTO)

Specify the expected number of hours upper limits to be used. The possible values are:

*ALL: Do not use the upper limits of the expected number of hours as a selection field. All values are valid.

date: Specify the expected number of hours upper limits.

Realized number of hours from (ERFR)

Specify the realized number of hours lower limits to be used. The possible values are:

*ALL: Do not use the lower limits of the realized number of hours as a selection field. All values are valid.

date: Specify the realized number of hours lower limits.

Realized number of hours until (ERTO)

Specify the realized number of hours upper limits to be used. The possible values are:

*ALL: Do not use the upper limits of the realized number of hours as a selection field. All values are valid.

date: Specify the realized number of hours upper limits.

Fix data (FDTA)

Specify what data must be printed and the format in which it must appear.

*SHORT: Prints only the basic amount of information. Use this value for rough reports.

*NONE: Prints no additional information. Some information (e.g. the fix number) will always be printed.

*DETAIL: Prints detailed information.

Request data (RDTA)

Specify the amount and kind of request data to be printed. The printed requests are the request connected to the selected fixes. The possible values are:

*SHORT: Prints only the basic amount of request information.

*NONE: Prints no request information.

*DETAIL: Prints detailed request information.

The possible ratification data values are.

*NONE: The print of ratification data is currently not implemented.

Solution data (SDTA)

Specify the amount of solution data to be printed. The printed solutions are the objects connected to the selected fixes. The possible values are:

*SHORT: Prints only the basic amount of solution information.

*NONE: Prints no solution information.

*DETAIL: Prints detailed solution information.

Specify whether the override information will have to be printed. The possible values are:

*NONE: No override information will be printed.

*SHORT: Override information will be printed for each solution, when available. The description belonging to the solution will be truncated, even when no overrides are found. Using this option, you are able to see on the report; whether a solution is merged, if applicable.

Output format (FMT)

Specify how the data must be formatted. The possible values are:

*COMPOUND: Prints the requested data in a combined form. The fix, request and solution information is printed together.

*LIST: The fix, request, and solution data is printed in separate lists.

Fix quality data (FQDA)

Specify if quality data has to be printed. The quality data is the data concerned with expected and realized dates. The possible values are:

*NONE: Do not print quality data.

*SHORT: Prints a list of the selected fixes. In this list, the differences between expected and realized dates and hours are printed.

*DETAIL: Prints a detailed list of fixes and the exact expected and realized dates.

Request quality data (RQDA)

Specify if the request dates have to be compared with the actual fix and request dates. The possible values are:

*NONE: Do not print request quality information.

*SHORT: Print a brief list of requests and compare the request dates with the actual dates.

Processing indicators (PRC)

The processing indicators enable you to steer the interface and some of its formatting. The following attributes can be specified.

Close indicator

Indicate if the interface has to be closed. The possible values are:

*YES: Files are closed and storage is freed. Subsequent requests must establish a new connection to the information.

*NO: Keep the interface to the information when the function exits. The same data paths are used which makes the interface considerably faster when subsequent requests are made.

Application per page

Specify if the function has to start printing on a new page if the application code changes. The possible values are:

*NO: Do not skip to a new page.

*YES: Skip to a new page.

Fix per page

Specify if each fix has to be printed on a separate page. The possible values are:

*NO: Do not skip to a new page when a new fix is started.

*YES: Skip to a new page when a fix is started.

Request per page

Specify if each request has to be printed on a separate page. The possible values are:

*NO: Do not print each request on a separate page.

*YES: Print each request on a separate page.

Solution per page

Specify if each solution must be printed on a separate page. The possible values are:

*NO: Do not print each solution on a separate page.

*YES: Print each solution on a separate page.

Print cover page

Specify if a cover page has to be printed with additional information. The possible values are:

*NO: Do not print the cover page.

*YES: Print the cover page.

Print end page

Specify if a closing page has to be printed with additional information. The possible values are:

*NO: Do not print the end page.

*YES: Print the end page.

Close print file

Specify if the subsequent print request has to direct their output to the same spooled file. The possible values are:

*YES: The print file is closed. Subsequent requests print to a new spooled file.

*NO: The print file is not closed. This value is valid only in combination with the "Close API indicator". Subsequent requests print their output to the same spooled file.

UOA:OMQPRTFI

Print Fix (OMQPRTFI) - Help