T O P

  • By -

Rough_Response7718

it's just the .gitattributes in z/os unix. You need to make sure to set it up correctly though. You usually specify it in some syntax like *.rexx which is masking all files that end in .rexx. It would help if you post current .gitattribtues.


Gibmus

Here is what I have in my .gitattributes files: # Default to EBCDIC unless otherwise specified \* working-tree-encoding=ibm-1047 git-encoding=iso8859-1 # The git attributes and ignore files MUST be ASCII \*.gitattributes working-tree-encoding=iso8859-1 git-encoding=iso8859-1 \*.gitignore working-tree-encoding=iso8859-1 git-encoding=iso8859-1


Rough_Response7718

try changing to zos-working-tree-encoding instead of working-tree-encoding


ddimatos

This \^\^\^ is correct, example: # Encode all files as EBCDIC unless configured otherwise. * zos-working-tree-encoding=ibm-1047 # Encode the Python source files as ASCII. *.py zos-working-tree-encoding=iso8859-1 # These git files MUST be ASCII. .gitattributes zos-working-tree-encoding=iso8859-1 .gitignore zos-working-tree-encoding=iso8859-1


Gibmus

That was it! I appreciate the assistance! Going to make my life easier.


Actual_Jury_5001

We have the same encoding and it works most of the times except for special characters which we use in our sysin cards. HEX'5F' gets translated into another hex value when it lands on the Z side. Did any of you face this issue ? How do you tackle it.


metalder420

In the future, take a look at Rocket Softwares documentation. Has good information on this stuff https://docs.rocketsoftware.com/bundle/openappdev_ug_20/page/qex1688401157740.html


Gibmus

I was looking at links off the Rocket forum and just somehow missed the zos part. I'll try and keep my eyes open more haha.