How are CONSOLES specified in AOM using a z/OS V1.4 Operating System?

Document ID : KB000055251
Last Modified Date : 14/02/2018
Show Technical Document Details

Description

'AOM START' fails...                                                        
===============================================================================
AOM START                                                                   
N85704 AOM START COMMAND ACCEPTED.                                          
N85723 AOM START FAILED, REASON, SUBREASON 030-000.                         
N85724 DESC: CONS ALLOC FOR SCREENING TABLE FAILED.                         
N86O80 JES SCS FUNC=ALLOCATE ERROR, RC: 4 USERID: OP50AOMP - AREAS FOLLOW
PLIST    +000  E2C3E2D9 03854000 00000000 00000000   SCSR .e . .... ....    
PLIST    +010  D6D7F5F0 40404040 00000000 00000000   OP50      .... ....    
PLIST    +020  00000000 00000000 00000000 00000000   .... .... .... ....    
PLIST    +030  08A83F70 00000000 00000000 00000000   .y.. .... .... ....    
PLIST    +040  00000000 00000000 00000000 00000000   .... .... .... ....    
JSCC     +000  00000000 00000000 D1E2C3C3 08A81764   .... .... JSCC .y..    
JSCC     +010  08A81A18 60800000 00000000 00000000   .y.. -... .... ....    
JSCC     +020  00000000 00000000 00400000 00000000   .... .... . .. ....    
JSCC     +030  00000000 00000000 D6D7F5F0 C1D6D4D7   .... .... OP50 AOMP    
===============================================================================
The environment is z/OS V1.6 and SOLVE:Operations Automation V5.0 (SP1).    
The customer is runing with 'SYSPAMRS AOMCTYPE=JES'.
The output from the '/PARMS' option, 'CONSOLES - CONSOLE SPECIFICATIONS'...
===============================================================================
+- CONSOLES - CONSOLE SPECIFICATIONS ---------------------------------+     
| TYPE OF CONSOLES TO ACQUIRE .................+ JES                  |     
| MAX CONSOLES TO ACQUIRE ...................... 20                   |     
| MAX CONSOLES TO RETAIN ....................... 10                   |     
===============================================================================  

Solution

IBM CONSOLxx definitions were changed with z/OS V1.4. The following is part of the descrition about the 'CONSOLxx NAME' parameter from the IBM manuals...

===============================================================================
[z/OS V1R2.0 MVS Planning Operations]                          
Define each Console by Device Number and Device Unit on the CONSOLE 
statement and name each MCS Console.                                 
Console Names are recommended for all CONSOLE statements in 'CONSOLxx'.
Console Names are required for SMCS Consoles and optional for other types of
Consoles.                                                   
===============================================================================
?and?
===============================================================================
[z/OS V1R4.0 MVS Planning Operations]                                
Define each Console by Device Number and Device Unit on the CONSOLE 
statement and name each MCS Console.                                 
Console Names are required for all CONSOLE statements in 'CONSOLxx'.
===============================================================================
So, for z/OS V1.4 and above, the NAME parameter is required for JES/SS Consoles, eg...
CONSOLE DEVNUM(SUBSYSTEM),AUTH(ALL),NAME(consolxx)