This is an IBM Automation portal for Cloud Platform products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
When running UCD packaging v1 the variable file mentioned above (sidefile) is taken care of properly, gets copied to zOS the correct way and can be used as is.
When running UCD packaging v2 the variable file mentioned above (sidefile) is NOT taken care of properly, gets corrupt during copy to zOS and CAN'T be used at all.
The info we have got from our IBM representatives after their contact with the UCD team is this:
Packaging with UCD v2 format any member stored as VB and BINARY does not restore the same layout while it is loosing new lines.
If the files would not contain low values like a HEX 15, 25 there would be no problem.
However the SYSADATA file is most likely containing a lot of low values. Only UCD package format v1 works for these files.
We would like to have the same functionality in UCD Packaging v2 as the one already present in UCD Packaging v1 for the files mentioned above.
#
# assembler sysadata data set
assembler_sysadataPDS=${hlq}.SYSADATA
assembler_sysadataOptions=cyl space(5,5) lrecl(32756) dsorg(PO) recfm(v,b) blksize(32760) dsntype(library)
UCD Packaging stuff CreateUCDComponentVersion):
containerMapping = {"LOAD" : "LOAD", "ADATA" : "BINARY" ...
File on zOS should look like this:
BROWSE SYSADATA(TESTASM1 CORRECT) Line 0000000000 Col 001 080
Command ===> Scroll ===> CSR
********************************* Top of Data **********************************
....................
............É{O.ù·. ..
...........º2025010808495696-2341.6.0 ..UI97447 z/OS 03.01.00 TESASS
...........4.......................Ö...............´...........è................
...........Z"I..å.gµØ.0q.Ø.........047C.EN ..UNI .... ........Ö.....¢...
................................................... ............TESTASM1
etc...
But looks like this on zOS:
BROWSE SYSADATA(TESTASM1 INCORRECT) Line 0000000000 Col 001 080
Command ===> Scroll ===> CSR
********************************* Top of Data **********************************
................................Éá.d.æPØ.............y2025010907315696-2341.6.0
........... .......`.....................P.......Í...................H..........
******************************** Bottom of Data ********************************
Idea priority | Medium |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Thank you for submitting this idea. We will create a discussion topic with our mainframe development team to review this request. We will be in touch with you with updates soon. Thank you again.