Skip to content
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

Open
DcsOSG opened this issue Mar 30, 2022 · 9 comments
Open

[BUG] #437

DcsOSG opened this issue Mar 30, 2022 · 9 comments

Comments

@DcsOSG
Copy link

DcsOSG commented Mar 30, 2022

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

image

image

image

image

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

@lbdyck
Copy link
Collaborator

lbdyck commented Mar 31, 2022

Thank you for reporting this - we are aware that ZGBATCH (and ZG) are both in need of updating and are working on it.

@DcsOSG
Copy link
Author

DcsOSG commented May 18, 2022

Hi, I have tried to run ZGBATCH in V3R14 and the commit is not working as expected. Can you please advise?
ZGBATCH
ZGBATCH.txt

@MN-Mike
Copy link

MN-Mike commented May 18, 2022 via email

@DcsOSG
Copy link
Author

DcsOSG commented May 19, 2022

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.

ZGBATCH.txt

image

image

image

@MN-Mike
Copy link

MN-Mike commented May 24, 2022

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:
PROFILE PREFIX(TSUASKW)
ISPF CMD(%ZGBATCH TSUASKW 0 /u/tsuaskw/zigi/tsuaskwMV c)

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
this repository
qualignr - the Ignore qualifier number used by ZIGI
omvsfs - the directory where of the Git repository managed by
ZIGI
compush - (C) for commit, (P) for push
C (the default) performs commit only.
P performs both commit and push.

@DcsOSG
Copy link
Author

DcsOSG commented May 25, 2022

i am getting the following error:
warning: unable to access '//.config/git/attributes': EDC5047I An invalid file name was specified as a function parameter.
fatal: can't add ".zigi/ZZMFS.PROD.JCL": file tag (MIXED) does not match its attributes (IBM-1047)

@MN-Mike
Copy link

MN-Mike commented May 26, 2022

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:

# This .gitattributes file is autogenerated with ZIGI v3r13
*   git-encoding=utf-8 zos-working-tree-encoding=IBM-1047
.gitattributes    git-encoding=utf-8 zos-working-tree-encoding=iso8859-1
.gitignore        git-encoding=utf-8 zos-working-tree-encoding=IBM-1047
.zigi/*           git-encoding=utf-8 zos-working-tree-encoding=IBM-1047

Then execute the command ls -lT .zigi - all the files in the .zigi folder should have a tag of IBM-1047.
If not execute the command chtag -tc IBM-1047 .zigi/*

then see if that addressed the issue, good luck.

@DcsOSG
Copy link
Author

DcsOSG commented May 27, 2022

We upgraded to v3r14 from Vv3r12 skipping V13. Would this cause an issue?

@MN-Mike
Copy link

MN-Mike commented May 31, 2022

Not that I can think of.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants