02.05.2013 Views

MKS Implementer 2006 Administration Guide

MKS Implementer 2006 Administration Guide

MKS Implementer 2006 Administration Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Appendix A: <strong>Implementer</strong> Data Areas and User Exit Programs<br />

408<br />

Allow Member/Object on Multiple Requests (IMMULTRQS)<br />

The IMMULTRQS data area controls whether a member/object is allowed on multiple open<br />

promotion requests concurrently.<br />

Valid values for the data area are *NO or *YES enclosed in single quotes. The default value<br />

‘*NO’ does not allow an item on multiple promotion requests. Set the value to *YES to allow<br />

an item on multiple promotion requests.<br />

LANSA Error Messages (IMLNMSG)<br />

The IMLNMSG data area allows you to store the message IDs of LANSA errors you want to<br />

force a request to fail on when the error occurs during promotion processing. Fatal messages<br />

automatically cause the promotion to fail. During promotion, <strong>Implementer</strong> compares the<br />

message IDs written in the spool file of the export list to the message IDs recorded in the<br />

IMLNMSG data area. When a match is established, processing of the promotion job ends.<br />

This default data area value is blank. To store multiple messages IDs, separate the message<br />

IDs with a blank space.<br />

LANSA Partition Security Officer (IMLNPSO)<br />

The IMLNPSO data area allows you to store the name of the LANSA partition security<br />

officer. <strong>Implementer</strong> runs the LANSA command for export/import using the partition<br />

security officer profile to prevent migration failures caused by insufficient authority to the<br />

LANSA command and the items being exported.<br />

The data area is located on both the host system and the remote system and must be set on<br />

each system. The default data area value is blank. To change the data area, specify the<br />

partition security officer name in positions 1 through 10.<br />

LANSA Task Usage (IMLNTSK)<br />

The IMLNTSK data area allows you to enable LANSA task tracking in <strong>Implementer</strong>. Task<br />

tracking allows <strong>Implementer</strong> to process LANSA tasks as project numbers by creating an<br />

<strong>Implementer</strong> project record from the specified task number (if it does not already exist).<br />

The default data area value is *NO. Set the value to *YES to enable task tracking and for<br />

integration with Visual LANSA. For details, see “LANSA Task Tracking” on page 332 and<br />

“Visual LANSA” on page 332.<br />

Creation Commands That Allow the TGTRLS Parameter (IMPRVCMDS)<br />

The IMPRVCMDS data area allows you to store a list of creation commands that accept the<br />

Target Release (TGTRLS) parameter to perform local compiles for a remote environment.<br />

You can add other creation commands to the data area, although you do not need to change<br />

it often. For example, adding a command can be required if a new object is created by an<br />

upgrade to the operating system and you do not have the required version of <strong>Implementer</strong>.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!