An end-user tried to copy a sysout from View to a dataset, using the "Print to Dataset" function, but the dataset didn't have sufficient space receiving an E37-04 condition.
The VTAM SARXMS task took exclusive control of the dataset, even though they logged off from VIEW.
Is there a way to release the enqueue on that dataset ?
Release : 14.0
The client was doing a "Print to Dataset" function in View, which took control of the dataset being written, as the dataset had run out of allocated space to do the printing.
The only way to remedy a View SARXMS VTAM interface STC having exclusive control on a dataset being written, using the "Print to Dataset" function, would be to recycle (stop and start) the SARXMS task related to the VTAM that is mentioned.
10/18/2023 - Removed potentially sensitive data - Removed screenshots with customer info.