ZWEL0157E message inconsistency

[dkelosky]

I had a zwe config|install error (I forget which) that gave two somewhat related errors:

Error ZWEL0157E: Zowe Caching Service VSAM data set Non-RLS volume (zowe.setup.vsam.volume) is not defined in Zowe YAML configuration file.

Error ZWEL0157E: Zowe Caching Service VSAM data set name (components.caching-service.storage.vsam.name) is not defined in Zowe YAML configuration file.

In one message, Non-RLS but is absent from the other message. I didn't know "RLS" and found this doc:

https://www.ibm.com/docs/en/zos/2.1.0?topic=mode-using-vsam-record-level-sharing

It states:

VSAM record-level sharing (RLS) is an access option for VSAM data sets.

However, the message talks about Non-RLS volume. Does the attribute apply to the volume or data set?

[achmelo]

The first message says that VSAM is using the NORLS option in the vsam.volume property. There are 2 options available in zowe.yaml, in case you choose RLS, this will not be printed. The second message says you did not provide VSAM name. I am no VSAM expert, but it should be related to data set VSAM data set with Record-Level-Sharing enabled or not

[balhar-jakub]

Apart from the question, @dkelosky, if I understand the request properly, you ask us to have different IDs for these messages.

[dkelosky]

Apart from the question, @dkelosky, if I understand the request properly, you ask us to have different IDs for these messages.

I think yes, it feels like overloading of the ZWEL0153E message ID. I'm open to other opinions on this though.

Secondly, I am also not a VSAM expert, but it seemed like from the documentation an attribute of the data set itself, not the volume.

[balhar-jakub]

The ask therefore is to:

• change ID for one of the messages and reflect it properly in documentation and Troubleshooting
• For data set Non-RLS volume message make sure that it is correct factually

[dkelosky]

Thanks @balhar-jakub - for the first part, I've definitely seen traditional WTOs that have part of their message substituted. However, it makes providing an a system programmer response a little more difficult if each response is a bit different. For example, the WTO messages I've typically seen have a familiar format, see [IKJ736E](https://www.ibm.com/docs/en/zos/2.2.0?topic=messages-ikj736e)

Explanation This message is issued when the attempt to switch to a new broadcast data set fails. TSO/E received an unexpected return code from ENQ processing.

System action The current broadcast data set remains active.

Operator response Issue the command again. If it continues to fail for the same reason, contact the system programmer.

System programmer response Look up the return code for the ENQ macro in the z/OS MVS Programming: Authorized Assembler Services Reference EDT-IXG.

Source Time Sharing Options Extensions (TSO/E)

Routing code -

Descriptor code 5