VOX and OPS sessions cannot be found after upgrading Automation Point

Products

• Automation Point

Issue/Introduction

 When invoking a rexx program from the command window the following error messages are received: 

AXC0316W Invalid Session name VOX 
AXC0301E Input: MSGID(VOX62) SESSION(VOX) COLOR(TURQUOISE) 
AXC0316W Invalid Session name VOX 
AXC0301E Input: MSGID(VOX61) SESSION(VOX) COLOR(PURPLE) 
AXC0316W Invalid Session name VOX 
AXC0301E Input: MSGID(VOX5999) SESSION(VOX) COLOR(GRAY) 
AXC0316W Invalid Session name VOX 
AXC0301E Input: MSGID(VOX5122I) SESSION(VOX) COLOR(BRIGHT GREEN) 
AXC0316W Invalid Session name VOX 
AXC0301E Input: MSGID(AXC1105I) SESSION(VOX) COLOR(BRIGHT RED) 
AXC0316W Invalid Session name VOX 
AXC0301E Input: MSGID(AXC1104I) SESSION(VOX) COLOR(BRIGHT GREEN) 
AXC0316W Invalid Session name VOX 
AXC0301E Input: MSGID(*) SESSION(VOX) COLOR(WHITE) 
AXC0316W Invalid Session name OPS 
AXC0301E Input: MSGID(*) SESSION(OPS) COLOR(YELLOW)

Cause

The error messages above are telling you that the VOX and OPS internal sessions cannot be found, so evidently your Notification Messages (VOX) and OPS/MVS Messages (OPS) function windows that correspond to these sessions are not enabled at runtime. 

Resolution

1. Open Configuration Manager -> Expert Interface -> Automation -> Session Definition Sets

2. Scroll down to the Function Windows section. You will that the Notification Messages and OPS/MVS Messages function windows have an 'X' mark.

3. Select the Notification Messages function window and right-click. 

4. Select 'enable' from the context menu. You will then see an '*' mark next to this session.

5. Right click this same item again, and select "apply changes to runtime."

6. Apply steps 3-5 above to the OPS/MVS messages function window.

7. Now you can recall the command to invoke your REXX program and you should not see these error messages.