NL3 screen MSGID allocation has reached the maximum limit of 'ZYFFFF'
search cancel

NL3 screen MSGID allocation has reached the maximum limit of 'ZYFFFF'

book

Article ID: 235190

calendar_today

Updated On:

Products

CA 2E

Issue/Introduction

 CA 2E product release 8.7 is generating - Message: NL3 screen MSGID allocation has reached the maximum limit of 'ZYFFFF'. Contact customer support. 

Environment

Release : 8.7

Component : CA 2E

Cause

NL3 screen MSGID allocation has reached the maximum limit

Resolution

IMPORTANT: PLEASE TAKE THE BACKUP OF THE MODEL AS MANDATORY BEFORE EXECUTING THE BELOW SCENARIOS.

SOLUTION:

There are 2 scenarios as a solution for this issue: One is by resetting the Model value YPMTNBR to “AAAAAA” causing to reuse the gaps and creating the screen message IDs with existing prefix code that is “M”

We can keep the existing value of ALCCHR = ‘M’ for GENSEUTYP = 'SCM' and simply by changing the model value YPMTNBR to “AAAAAA” will reuse the gaps.

 

STEP1:-

            Set the model value YPMTNBR to ‘AAAAAA’

             YCHGMDLVAL MDLVAL (YPMTNBR) VALUE (AAAAAA)

SCENARIO-2:-

In second scenario, we can change the screen message ID prefix to different character in the “YGENTYPRFP” model file and reset the Model value YPMTNBR TO “AAAAAA”. In this scenario, new sequence of screen message IDs will be created with prefix collect from the YGENTYPRFP.

We have a Model File “YGENTYPRFP” (MDL Generation type), which contains the Name allocation character for each CPF source type. In case of SCM, we do have ‘M’ and by changing this value of ‘M’ to any other character will give new sequence of Message ID generation for Screen

STEP1:-

RUN THE FOLLOWING SQL statement

 UPDATE YGENTYPRFP SET ALCCHR = ‘N’ WHERE GENSEUTYP = 'SCM'    [we have changed ALCCHR to “N” in this example, and can be changed to any character]

 

STEP2:-

Set the model value YPMTNBR to ‘AAAAAA’

YCHGMDLVAL MDLVAL (YPMTNBR) VALUE (AAAAAA)