Generation of a REXX script using CA Verify for CICS results in error message "PTE60023 - UNABLE TO TYPE BECAUSE SESSION NOT ACTIVE ON PORT"?
search cancel

Generation of a REXX script using CA Verify for CICS results in error message "PTE60023 - UNABLE TO TYPE BECAUSE SESSION NOT ACTIVE ON PORT"?

book

Article ID: 46702

calendar_today

Updated On:

Products

Verify

Issue/Introduction

While generating a REXX script CA Verify for CICS produces the following messages:

/* THIS REXX EXEC RECREATES A SESSION CAPTURED BY CA VERIFY. */
TRACE ?I
ADDRESS VERIFY
" MONITOR SIGNALS "
" LOGON '<logonid>' ",
" MODEL 'D4A32782' 24X80 24X80 BASICDS "
" INVITE 0500 "
 
" TYPE CLEAR "
/* */
/* */
/* */

When this is submitted there is an error on the clear statement stating that there is no CICS Port:

P1 HALT(FAULT): PTE60023 - UNABLE TO TYPE BECAUSE SESSION NOT ACTIVE ON PORT
7 +++ " TYPE CLEAR "
IRX0004I Error running SECLOG1, line 7: Program interrupted

Environment

Release: OSVERW00200-8.5-Verify-Automated Regression Testing-for VTAM Extended Environment

Resolution

There is some VTAM setup that is required for the REXX feature that is not documented in the Verify for CICS configuration.  It seems that some setup for the REXX feature assumes that the customer has installed Verify for VTAM which is not the case here.

There are two sample members (AQ8MODEA and AQ8LIST) from hlq.CATJJCL which are only distributed to CA Verify for VTAM customers.  The two sample members will create the combined logon mode table XTCAMODE and the VTAM definitions needed for REXX support.

Updating VTAM should get past the original LOGON error.  You might also need to add the CA Verify virtual terminals VTERM001 through VTERM050 to your DOORS database in order to enable those terminals to auto-install in the CICS region.