WSTOMINS fails with "cp: FSUM6260 write error" and EDC5003I
Article ID: 275788
Updated On:
Products
Issue/Introduction
Endevor Web Services first time installation ends with: ÝINFO¨ Log saved in: /tmp/CA_temp/wstomins/logs/WSInstaller-2023-11-03.log ================================================================================ **** Installation complete **** ================================================================================ cp: FSUM6260 write error on file "//'&OPSYS.xx.ENDEVOR.CSIQJCL.WSTOMINS(WSTOMSTC)'": EDC5003I Truncation of a record occurred during
The error is in the RUNSCRIPT part of the process where the install script (ENWSIns.sh) is trying to edit the //STDENV statement in the SWTOMSTC output dataset.
It seems the sed regex is not working as expected as it appears to write the first part of the output line multiple times (looping) and then gets a truncation error when it tries to copy the temp file back to the target library.
What is seen in the target library (after truncation) is:
//STDENV DD DISP=SHR,DSN=//STDENV DD DISP=SHR,DSN=xxx.ENDEVOR.CSIQJCL.WSTOMIN
What is expected is something more like:
//STDENV DD DISP=SHR,DSN=xxx.ENDEVOR.CSIQJCL.WSTOMINS(&ENV)
Environment
Endevor Web services
Release: 19.0
Cause
The customer has an ampersand ("&") at the start of their WSTOM_DATASET because they are using system variable &OPSYS i.e.WSTOM_DATASET="&OPSYS.xx.ENDEVOR.CSIQJCL.WSTOMINS"
Endevor Engineering advised that the ampersand is a special character in terms of the sed command replace string on line 180 of the ENWSIns.sh.txt file and that is causing the error.
Resolution
The user worked around the problem by hard coding the data set name instead of using &OPSYS.
This future resolution was also agreed with the user:
The &OPSYS symbol should just be interpreted by the script, leading to the exact same behavior when WSTOMINS is submitted as if it had:WSTOM_DATASET="xxx.ENDEVOR.CSIQJCL.WSTOMINS".
This would enable having a single WSTOMINS submitted on multiple systems.
To achieve this the simple fix is to change SYMBOLS=JCLONLY in the WSTOMINS job to SYMBOLS=EXECSYS to ensure the symbol is resolved correctly.
This change will be added by Engineering in a future fix.
Additional Information
Feedback
