CICS Bundles have limited obvious scope for documentation

When creating CICS Bundle in CICS Explorer there initially appears to be very limited scope to include any description or documentation within the bundle itself.

• A CICS Application Bundle has a description field of up to 255 characters which is not present in a CICS Bundle Project.

• Individual items within a Bundle such as event binding have some space for a description.

• An event binding and event adapter resource in a binding has what appears to be a bigger field but quickly gives an error message "Value is longer than expected" with no indication what the length is but experimenting suggests it is 256.

Experimenting has revealed that any file can be added to the bundle such as "Readme.txt" but it requires a user to decide to do this. On exporting the bundle to a z/OS Unix File system all files in the bundle are transferred as binary files. I cannot really call this transferring the extra files as a bug after all I am not using the bundle as designed but am suggesting that:

At a minimum, a Readme file is created as part of the bundles by CICS Explorer which gives more intuitive scope for documentation within the Bundle itself or at least a reference to where it is.

Transferring the files not required by CICS runtime to z/OS does not cause a problem beyond using more DASD but I do have these possible actions in mind.

1. Do not transfer files not required by the CICS runtime.

2. Ask the user if the extra files should be transferred - preferably whether ascii or binary should be used.

3. As above but file by file with a "same answer for all the rest" option.

4. The ability to tag the extra files in advance - a bit more of a Gold Standard.