TMP_HLQ - Lineinfile #834
Replies: 7 comments 3 replies
-
|
Just to complement the information, I found an error in the zOS log, indicating that the automation is trying to access the master catalog, but if it was using the qualifier inserted in tmp_hlq and it was trying to write DST.ASBCIC01.** instead of ASBCIC01.* * this would not be happening.
|
Beta Was this translation helpful? Give feedback.
-
|
Hi @fabiobncbb , I'll try to recreate but I'll do so on a supported version of zoau. Ansible z/OS core 1.6.0 requires minimal zoau 1.2.2. We don't perform recreates on unsupported combinations. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I will answer the second question first, currently our tmp_hlq does not allow for more than one single segment meaning it must be no more than 8 characters long allowing for [A-Z]{1}[A-Z0-9]{0,7}.
If this is something you wish to be supported, please open an "Enhancement" issue so this can be triaged and then prioritized against other current and backlog entries. |
Beta Was this translation helpful? Give feedback.
-
|
I have opened issue #909 to correct some of my findings, please review it when you can. |
Beta Was this translation helpful? Give feedback.
-
|
To address your first issue, although I did not see your playbook, my guess is that you are using For now, your work around is:
Results with backup_name
Output: see issue #910 |
Beta Was this translation helpful? Give feedback.
-
|
Hi! I'm not using backup and I'm getting the same error accessing the master catalog, both in the zos_lineinfile and zos_copy modules, using or not using the tmp_hlq parameter. This is my task zos_copy: This is the result with -vvvv TASK [cria_proclib : Faz uma cópia da proc do cics modelo e salva com o nome do cics novo] ******************************************************************************************************************************* This is the error in the zos log, which shouldn't happen if you were using tmp_hlq correctly, because it shouldn't access the master_catalog, but a user_catalog. ICH408I USER(ASBCIC01) GROUP(OMVSGRP ) NAME(ANSIBLE CICS USER 01) 243 I'm using ZOA 1.2 and zos_core 1.6 |
Beta Was this translation helpful? Give feedback.
-
|
@fabiobncbb Thank you for this information, it makes troubleshooting easier. There are a few things here happening, first lets back up and explain something that that is corrected in 1.7.0-beta.1 coming out in about a week. In 1.5.0 - 1.6.0 because the zos_copy module had been redesigned completely, the team added a 'automatic' backup strategy meaning we performed a backup no matter what even if we were not asked to, then on success removed it; this was a data integrity safety check that we probably should have never introduced, thus its being removed in 1.7.0-beta.1. In 1.6.0 we allowed users to bypass the automatic backup with
I think the error ""Source data set DSS.PLEXDES.PROCLIB.CTG(CIC0A0Z) does not exist"," is because a LISTCAT was performed to see if the data set existed and was cataloged, your user For src and dest, you should be setting the HLQ, in other words, There is temporary data sets used when we invoke LISTCAT, LISTDS, and other VTOC commands, but this time I did not see any error for that. For example in your first I don't need a recreate to see that our commands to call LISTCAT, LISTDS, and other VTOC are not passing tmp_hlq; could you try my zos_copy suggestion above and for zos_blockinfile set the GLOBAL environment var ` |
Beta Was this translation helpful? Give feedback.
-
|
Hi @ddimatos! I figured tmp_hlq was just for the temporary files that the user would never need to see or know existed, like these and that he wouldn't put that tmp in front of the scr ever.
Unfortunately I can't put the tmp_hlq in the scr, because that would change the path where it would look for the old member and create the new one, as the correct path is DSS and not DST, as below: Translate the path: DSS is the path to the member and DST was the path just to temprary files ASBCIC01.** (DST.ASBCIC01.**) I also couldn't put DSS as tmp_hlq because DSS libraries need much more permissions and access rules than DST (temporary) libraries and since the idea is that they were only used for temporary files that would be deleted at the end of the run, DST would be the best choice. Today I managed to resolve the situation. As? zos_copy: The issue is that this alias is different from the standard of our environment (it is not allowed to create aliases for users, only for applications) and I don't know if I will be able to create this alias in the production environment, so I wanted to understand why it is not working, but I also believe that, as a new version of the module is about to be released, it is not worth the effort to discover the cause and we can close this discussion. |
Beta Was this translation helpful? Give feedback.
-
|
It was a bit difficult to follow without additional details; it looked to me like the error for zos_copy was In the Despite the confusion, there is an issue, the code that drives the discover of data sets is not taking into consideration the tmp_hlq, that is a bug, and I will open an issue for it. This impacts nearly every module that is working with a data set, 1.7.0-beta.1 does not address this issue, it will persist there. I do not know if you saw my comment but there is a way to achieve a temporary high level qualifier which is what we offered in 1.4.0 and still exists, that is to add the environment variable Ill share what that looks like once more, see the last variable |
Beta Was this translation helpful? Give feedback.
-
|
I will close the issue as you suggested but leave it unlocked so updates can be provided. It would be good to know if the environment var workaround |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi guys!
I'm using the new parameter tmp_hlq in zos_lineinfile but I'm still having problems executing an automation. I couldn't confirm if the automation is using this hlq, since the error shows the file name without the selected hlq.
Another thing I would like to confirm is: Can I use more than one qualifier in HLQ? As? In my environment I would like to use: "DSS.CIC", but it does not accept it and gives an error in the qualifier:
Note: In the lab environment, I was able to solve the problem by deleting the tmp_hlq parameter and granting access to the master catalog to the automation user, but in the production environment this access is blocked.
My environment is using ZOAU 1.2 and zos_core 1.6.0
Beta Was this translation helpful? Give feedback.
All reactions