Fixes the issue in processAnalyticsFromLogFile as reported by @AnthonyGiorgio by embedding date into utilities:
parse error: Invalid numeric literal at line 1, column 10
FSUM9364 Bad date conversion: 2023-10-06 10:42:29
Usage: date [-cu] [-d time] [+format]
Also embeds sha256sum, which would be used to verify the checksum matches the metadata.json's checksum
Note:
Another approach would be to embed coreutils (which includes date, sha256sum and many other tools). Another benefit of this is that we don't have to rely ascii workarounds like asciiecho (https://github.com/ZOSOpenTools/meta/blob/main/bin/zopen-build#L40) and we also can replace numcpus.rexx with nproc. It will increase size by 14mbs though.
This is fine but can you create another issue so that we can pick up fixes to date/sha256sum if they are required as part of the build process of meta?
Note: Another approach would be to embed coreutils (which includes date, sha256sum and many other tools). Another benefit of this is that we don't have to rely ascii workarounds like asciiecho (https://github.com/ZOSOpenTools/meta/blob/main/bin/zopen-build#L40) and we also can replace numcpus.rexx with
nproc
. It will increase size by 14mbs though.