Zowe V2.7 - STDENV OPEN FAILED

[codezfire]

Describe the bug Client recently applied zOS maintenance along with the following maintenance for ZOWE

UO02064 UO02065 UO02066 UO02067

Post IPL, when ZOWE task was started, it started throwing the following message. Could you please suggest on why the following messages show on the STDENV.

PARM='ENVAR(_CEE_ENVFILE=DD:STDENV)

$HASP708 ZWESLSTC STDENV OPEN FAILED
RC=03 DATA SET ALREADY OPENED
DSNAME=ZWESVUSR.ZWESLSTC.STC15637.D0000101.?
IEC141I 013-C0,IGG0199G,ZWESLSTC,ZWESLSTC,STDENV 345
$HASP708 ZWESLSTC STDENV OPEN FAILED
RC=03 DATA SET ALREADY OPENED
DSNAME=ZWESVUSR.ZWESLSTC.STC15637.D0000101.?
IEC141I 013-C0,IGG0199G,ZWESLSTC,ZWESLSTC,STDENV 347

To Reproduce Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Additional context Sysprint :

1//ZWESLSTC JOB MSGLEVEL=1 STC16262 //STARTING EXEC ZWESLSTC
1 J E S 2 J O B L O G -- S Y S T E M G O A A -- N O D E G O A A M V S
0 10.33.11 STC16262 ---- TUESDAY, 23 MAY 2023 ---- 10.33.11 STC16262 IEF695I START ZWESLSTC WITH JOBNAME ZWESLSTC IS ASSIGNED TO USER ZWESVUSR, GROUP ZWEADMIN 10.33.11 STC16262 $HASP373 ZWESLSTC STARTED 10.33.11 STC16262 IEF403I ZWESLSTC - STARTED - TIME=10.33.11 10.41.03 STC16262 $HASP708 ZWESLSTC STDENV OPEN FAILED 152 RC=03 DATA SET ALREADY OPENED 152 DSNAME=ZWESVUSR.ZWESLSTC.STC16262.D0000101.? 10.41.03 STC16262 IEC141I 013-C0,IGG0199G,ZWESLSTC,ZWESLSTC,STDENV 153 10.41.04 STC16262 $HASP708 ZWESLSTC STDENV OPEN FAILED 154 RC=03 DATA SET ALREADY OPENED 154 DSNAME=ZWESVUSR.ZWESLSTC.STC16262.D0000101.? 10.41.04 STC16262 IEC141I 013-C0,IGG0199G,ZWESLSTC,ZWESLSTC,STDENV 155 10.41.04 STC16262 $HASP708 ZWESLSTC STDENV OPEN FAILED 156 RC=03 DATA SET ALREADY OPENED 156 DSNAME=ZWESVUSR.ZWESLSTC.STC16262.D0000101.? 10.41.04 STC16262 IEC141I 013-C0,IGG0199G,ZWESLSTC,ZWESLSTC,STDENV 157 1 //ZWESLSTC JOB MSGLEVEL=1 STC16262 2 //STARTING EXEC ZWESLSTC
3 XXZWESLSTC PROC RGN=0M,HAINST='{{}}'
XX****/
XX This program and the accompanying materials are /
XX made available under the terms of the /
XX Eclipse Public License v2.0 /
XX which accompanies this distribution, and is available at /
XX https://www.eclipse.org/legal/epl-v20.html /
XX /
XX SPDX-License-Identifier: EPL-2.0 /
XX /
XX Copyright Contributors to the Zowe Project. /
XX****/
XX /
XX ZOWE LAUNCHER PROCEDURE /
XX /
XX NOTE: this procedure is a template, you will need to modify /
XX #zowe_yaml variable to point to your Zowe YAML config /
XX file. /
XX /
XX Check https://docs.zowe.org for more details. /
XX /
XX****/
4 XXZWELNCH EXEC PGM=ZWELNCH,REGION=&RGN,TIME=NOLIMIT,
XX PARM='ENVAR(_CEE_ENVFILE=DD:STDENV),POSIX(ON)/&HAINST.'
IEFC653I SUBSTITUTION JCL - PGM=ZWELNCH,REGION=0M,TIME=NOLIMIT,PARM='ENVAR(_CEE_ENVFILE=DD:STDENV), POSIX(ON)/{{}}' 5 XXSTEPLIB DD DSNAME=SYS1.ZOWE.SZWELOAD,DISP=SHR
6 XX DD DSNAME=SYS1.ZOWE.SZWEAUTH,DISP=SHR
7 XXSYSIN DD DUMMY
8 XXSYSPRINT DD SYSOUT=,LRECL=1600
9 XXSYSERR DD SYSOUT=
XX****/
XX
XX CONFIG= can be either a single path ex.
XX CONFIG=/my/zowe.yaml
XX Or a list of FILE() and colon : separated paths in the form of
XX CONFIG=FILE(/my/long/path/to/1.yaml)\
XX :FILE(/my/long/path/to/2.yaml)
XX
XX In the above case, the \ is used as a line continuation.
XX
XX When using a list, files on left override properties
XX From files to their right.
XX Typically the right-most file should be the Zowe default yaml.
XX*
XX****/
10 XXSTDENV DD *
STMT NO. MESSAGE 2 IEFC001I PROCEDURE ZWESLSTC WAS EXPANDED USING SYSTEM LIBRARY SYS1.PROCLIB IEF695I START ZWESLSTC WITH JOBNAME ZWESLSTC IS ASSIGNED TO USER ZWESVUSR, GROUP ZWEADMIN IEFA111I ZWESLSTC IS USING THE FOLLOWING JOB RELATED SETTINGS: SWA=ABOVE,TIOT SIZE=64K,DSENQSHR=DISALLOW,GDGBIAS=JOB IEF236I ALLOC. FOR ZWESLSTC ZWESLSTC IEF237I 5029 ALLOCATED TO STEPLIB IEF237I DMY ALLOCATED TO SYSIN IEF237I JES2 ALLOCATED TO SYSPRINT IEF237I JES2 ALLOCATED TO SYSERR IEF237I JES2 ALLOCATED TO STDENV IEF237I JES2 ALLOCATED TO SYS00001 IEC141I 013-C0,IGG0199G,ZWESLSTC,ZWESLSTC,STDENV IEC141I 013-C0,IGG0199G,ZWESLSTC,ZWESLSTC,STDENV

[JoeNemo]

Can this be reproduced by installing 2.5 and then upgrading to 2.7? I want to test whether this is system env vs. code.

Also check version of Launcher vs Scripts

[codezfire]

Here's an interesting similar error documented

https://knowledge.broadcom.com/external/article/14764/can-ceeopts-dd-be-coded-as-ceeopts-dd-i.html