-
Notifications
You must be signed in to change notification settings - Fork 23
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] #437
Comments
Thank you for reporting this - we are aware that ZGBATCH (and ZG) are both in need of updating and are working on it. |
Hi, I have tried to run ZGBATCH in V3R14 and the commit is not working as expected. Can you please advise? |
It looks like your path to the zFS Repo is all UPPERCASE. Is this correct? Remember this is a zFS path and the case needs to match, also it should point to the git working Directory (the folder that includes the .git and .zigi folders).
Your example has /GLOBAL/SOURCE/OSG/ZZMFS.PROD
From: DcsOSG ***@***.***>
Sent: Wednesday, May 18, 2022 12:58 AM
To: zigi/zigi ***@***.***>
Cc: Subscribed ***@***.***>
Subject: Re: [zigi/zigi] [BUG] (Issue #437)
Hi, I have tried to run ZGBATCH in V3R14 and the commit is not working as expected. Can you please advise?
[ZGBATCH]<https://user-images.githubusercontent.com/102647756/168967470-fad14c41-1e2e-46a2-8067-d954f6890d89.PNG>
ZGBATCH.txt<https://github.com/zigi/zigi/files/8713575/ZGBATCH.txt>
—
Reply to this email directly, view it on GitHub<#437 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AO7Z4N5ZDA4IOMFYRLSH7L3VKSBHJANCNFSM5SDMHM4Q>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.******@***.***>>
This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or intended recipient’s authorized agent, the reader is hereby
notified that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.
|
Hi, yes repo is /global/source/osg/ZZMFS.PROD You can see in the txt file that repository is correct but commit isn't performed. Might be user error on my part. But not 100% sure. |
I am testing with 3.14 and it is working for me. The omvsfs value should be the working directory (where the .zigi and .git folders are). My test command is: Perhaps copy the full sustsprt output if this continues to fail. Just a reminder to the thread the command setup is: ISPF CMD(%ZGBATCH hlq qualignr omvsfs compush) hlq - HLQ/prefix used in ZIGI for datasets associated with |
i am getting the following error: |
I had the file tag issues before when I tried to initialize the folder without following the process exactly. There are a couple things you might check. See that the .gitattributes file in your working directory has the following lines in it:
Then execute the command then see if that addressed the issue, good luck. |
We upgraded to v3r14 from Vv3r12 skipping V13. Would this cause an issue? |
Not that I can think of. |
Describe the bug
Getting below messages after running JCL %ZGBATCH commit on a Z/OS environment:
Checking for changes in PDS: '.ZZMFS.PROD.JCL'
INVALID DATA SET NAME, '.ZZMFS.PROD.JCL'
IKJ58400I LISTDSI FAILED. SEE REASON CODE IN VARIABLE SYSREASON.
IKJ58401I ERROR PARSING THE STATEMENT. PARSE SERVICE RETURN CODE IS 0004
No changes detected
Checking for changes in PDS: '.ZZMFS.PROD.SOURCE'
INVALID DATA SET NAME, '.ZZMFS.PROD.SOURCE'
IKJ58400I LISTDSI FAILED. SEE REASON CODE IN VARIABLE SYSREASON.
IKJ58401I ERROR PARSING THE STATEMENT. PARSE SERVICE RETURN CODE IS 0004
No changes detected
Performing Git Processing . . .
On branch master
nothing to commit, working tree clean
On branch master
nothing to commit, working tree clean
warning: unable to access '//.config/git/attributes': EDC5047I An invalid file n
Git Processing completed.
READY
END
******************************** BOTTOM OF DATA ********************************
Release of ZIGI
V3R11
To Reproduce
Steps to reproduce the behaviour:
Create Repo.
Add a PDS to the repo.
Add all members (A besides the dataset name).
Commit.
Exit ZIGI.
Copy member 'ZIGI' to 'ZZMFS.PROD.JCL'
Run batch job %ZGBATCH to commit changes
%ZGBATCH doesn't realise that 'ZZMFS.PROD.JCL' has been updated so no commit is done
Will only work if I manually go into repository (ZZMFS.PROD) and then PDS realises that a modification has been made. Then I can rerun %ZGBATCH and commit will work.
Screenshots
warning: unable to access '//.config/git/attributes': EDC5047I An invalid file name was specified as a function parameter.
Additional context
Add any other context about the problem here.
Thanks,
John
The text was updated successfully, but these errors were encountered: