BRMS GUI Omit Migration

The WRKCTLGBRM *BKU option 3 (Copy) and the Create Control Group Based On (Q1ACRTCGBO) API have been enhanced to provide optional support to migrate control groups with GUI object omits to a control group using green screen object list with omits in release 5770-BR1 7.3 and later with the following PTFs:

7.5 SI78291
7.4 SI78290
7.3 SI78289

This function needs to be enabled before using WRKCTLGBRM *BKU option 3 (Copy), it is not the default behavior.

To Enable:

In 5770-BR1 7.3 and 5770-BR1 7.4 run one of the following commands:

CALL QBRM/Q1AOLD PARM('SETUPFUN' '*SET' 'Q1AMGROMIT' '*SYS') which enables the new functionality for all BRMS jobs.
CALL QBRM/Q1AOLD PARM('SETUPFUN' '*SET' 'Q1AMGROMIT' '*JOB') which enables the new functionality for the current signed on job only.

In 5770-BR2 7.4 and 7.5, and 5770-BR1 7.5 run the following command:

SETFCNBRM ACTION(*ADD) FUNCTION(MGROMIT) SCOPE(*SYS)

The SCOPE parameter also supports *JOB to only affect the current signed on job.

During the migration BRMS internally creates a backup object lists and adds it as a backup item to the copy control group. The format of the backup lists name is Onnnnnnaaa where nnnnnn is the current job number and aaa is unique sequence identifier.

Limitations To Using the Function

No special value support for control group entries *SAVSYS, *IBM, or *ALLDLO since these are not supported in an object or folder list. When BRMS copies these entries, the object omits will not be copied to the new control group.
A control group with GUI object omits cannot be copied to a remote system when migrating to a new control group. The new migrated control group which removed the GUI objects omits can be copied to a remote system.

Reusing a Control Group Name

Because the WRKCTLGBRM function does not have RENAME option, to convert a control group that contains GUI-created Omits into a new control group that uses backup object lists, you first must copy the old control group into a new control group. Next, delete the old control group. Then copy the new control group again; this time naming it the same as the original control group and delete that first copy.

Alternative Methods:

BRMS APIs

BRMS provides the following APIs to add and remove object level omits to control group entries.

The Create Control Group Based On (Q1ACRTCGBO) API

When using the the Create Control Group Based On (Q1ACRTCGBO) API, a new optional parameter has been added to indicate that the copy should migrate the object omits.

Required Parameter Group:
1	New control group name	Input	Char(10)
2	Based on control group name	Input	Char(10)
3	Control group type	Input	Char(10)
4	Copy control group entries	Input	Char(1)
5	Error code	I/O	Char(*)
Optional Parameter Group:
6	Migrate to object list omit	Input	Char(1)
Default Public Authority: *USE
Threadsafe: No

Required Parameter Group

New control group name

INPUT; CHAR(10)

Specifies the name of the control group that is being created.

Based on control group name

INPUT CHAR(10)

Specifies the name of the control group that is being used to create the new control group.

Control group type

INPUT CHAR(10)

Specifies what type of control group is to be created. Backup, Archive, or Migration are the 3 types. Only Backup is currently supported.

The possible value follows:

*BKU

A backup control group will be created.

Copy control group entries

INPUT CHAR(1)

Specifies if the entries in the control group should also be copied from the based on control group.

The possible values follow:

0

Specifies to not copy the entries.

1

Specifies to copy the entries.

Error code

I/O CHAR(*)

The structure in which to return error information. For the format of the structure, see Error Code Parameter.

Optional Parameter Group

Migrate to object list omit

INPUT CHAR(1)

Specifies if the copy control group should migrate existing GUI object omits to an object list using omits based on control group.

The possible values follow:

0

Specifies to not migrate the GUI object omits.

1

Specifies to migrate the GUI object omits.

Error Messages

CPF1E64 E Parmeter value * not valid for program *.
CPF24B4 E Severe error while addressing parameter list.
CPF3CF1 E Error code parameter not valid.
CPF5222 E Name is not valid.
CPF9800 E All CPF98xx messages could be signaled. Xx is from 01 to FF.
BRM1308 E Control Group * already exists.
BRM3C1E E Required parameter omitted.
BRM3C4B E Value not valid for field at offset *.
BRM3C4C E Value not valid for field at offset *
BRM3C91 E Product feature required.
BRM3C94 E Object not created.
BRM3C99 E Unexpected condition with * API. Reason *.
BRM402A E BRMS product initialization required.
BRM4040 E Access denied for user *.
BRM4107 E Length * not correct.
BRM4108 E Format name * not correct.

During the migration BRMS internally creates a backup object lists and adds it as a backup item to the copy control group. The format of the backup lists name is Onnnnnnaaa where nnnnnn is the current job number and aaa is unique sequence identifier.