-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Error using SET operator command with zos_operator #353
Comments
@dvdrbn-m9 looking into this so I can size the work, I want to try a few things before I have anything else to report. |
Thanks for your time! Tell me if I can help and test something. |
Thanks @dvdrbn-m9 i might take you up on that , I saw some particular code and I am not sure why it’s there… so if I edit it I may reach out to you , thanks for offering |
@richp405 - in 1.3.0-beta.2 we introduced the REXX code to run the operator commands likely because wanted to support WAIT allowing a user to configure the time to wait before returning on an operator command. Looking over this issue I do see that this line here does a evaluation of the command looking for QUERY, SET, etc
But something like this will:
Where Its odd to me be because I don't believe QUERY or WHO are operator commands and checking for a forward shlash and then removing it makes no sense. I know this is not in issue in the 1.5.0-beat.1 code that will not be out till late in 4Q because its all C code now but this is a problem in 1.4.0-beta.1 and we are about to release 1.4.0-beta.2, if we could get some time on this we might be able to get it in before we release. MVS command reference
|
The rexx was a bit awkward here... I can not reproduce to original issue that led to the search query, but my notes had an explanation involving simple (non-parameterized commands). I have an experiment to run, where the search is still in place, but the command gets a set of apostrophes, which should fix it. If that fails, we will need to strategize, because SET is not the same as /SET, as I understand it. That was why the check for SET and / was in there originally. |
The fix has been validated, and new tests added to the unit test system so we keep SET and QUERY working the way they should. |
Merged into |
SUMMARY
When using
SET
command with the zos_operator causes an error with the following message:If I use
T
, which is a shortcut toSET
, the task completes successfully.COMPONENT NAME
zos_operator module
ANSIBLE VERSION
SPECIFY ANSIBLE COLLECTION VERSION
1.4.0-beta.1
also tried with 1.3.5, same result
SPECIFY THE Z OPEN AUTOMATION UTILITIES VERSION
2021/08/05 22:12:58 CUT V1.2.0
ENVIRONMENT
z/OS v2.5
STEPS TO REPRODUCE
The following task should cause the issue:
This works:
EXPECTED RESULTS
Operator command ran and is visible in SYSLOG, task finishes successfully.
When running with
T
and-vvvv
:ACTUAL RESULTS
Nothing is written in the SYSLOG.
The text was updated successfully, but these errors were encountered: