VSAM property of caching-service never read?
Open
Nobody has claimed this yet.
bug
good first issue
Priority: Low
size/S
- Dominant language
- Java
- Stars
- 92
- Forks
- 81
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 46
Description
This line of code looks like only "components.apiml.storage.vsam.name" is checked.
Within the conditional, then "components.caching-service.storage.vsam.name" is referenced, but the logic seems like it won't get there.
Instead of
if [ -n "${ZWE_configs_storage_vsam_name}" ]; then
VSAM_FILE_NAME=//\'${ZWE_configs_storage_vsam_name:-${ZWE_components_caching_service_storage_vsam_name}}\'
fi
Perhaps this will work
if [ -n "${ZWE_configs_storage_vsam_name}" ]; then
VSAM_FILE_NAME=//\'${ZWE_configs_storage_vsam_name}\'
elif [ -n "${ZWE_configs_storage_vsam_name}" ]; then
VSAM_FILE_NAME=//\'${ZWE_components_caching_service_storage_vsam_name}\'
fi
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inspect apiml-package/src/main/resources/bin/start.sh around line 221 and trace the two VSAM environment variables used by the conditional. Done means the caching-service VSAM property can reach the intended fallback logic and the variable checks match the documented configuration names.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100