Help needed - Problem with tar files larger than 2 mb

[FALLAI-Denis]

Hi,

Failing to find a better place, and a bit lost in my research, I am posting here a request for help from the community on the use of the tar command in the USS context.
If the moderator considers that my request is inappropriate, he is authorized to delete it.

We use the tar command to package components built with zAppbuild/DBB.

We find that when the tar file reaches a certain size, around 2 mb, it contains "parasitic" information.
This information does not prevent reading the tar file on z/OS-USS, but prevents reading it on another operating system (Windows for us, same under Git Bash for Windows).
Tar files under 2mb have no garbage information and are readable on Windows (with the 7-zip utility).

Example of parasitic information present in the tar file:

/tmp/IBMOS390_USTAR_SUMMARY_1678790853

The tar file is created in one go from a previously prepared folder and sub-folders.

The command used is:

tar cUXf $tarFile *

We don't have much experience on the z/OS-USS system and our systems teams even less...

Maybe other zAppbuil/DBB users have encountered this issue and can help us fix it.

Thanking you in advance.

[FALLAI-Denis]

PS:

I think the /tmp/IBMOS390_USTAR_SUMMARY_1678790853 files are for extended attribute handling and that's not our problem.

On the other hand, when checking the file on Windows by the tar command contained in Git for Windows, we have this message at the end of the list:

/tmp/IBMOS390_USTAR_SUMMARY_1678799645 unknown file type ‘T’

[dennis-behm]

@FALLAI-Denis

This almost feels like a support case on the USS component (not DBB). Especially if it is reproducible .

The options UX will save all attributes to be restored on z/OS and non-z/OS systems, which leads to the IBMOS390_U.. information.

Do you run in the same issue when you don't pass the UX options?

Here is my bookmark:
https://www.ibm.com/docs/en/zos/2.4.0?topic=scd-tar-manipulate-tar-archive-files-copy-back-up-file