Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide the ability to view Library datasets (in external to CICS view) #43

Open
Tracked by #50 ...
JeffinSiby opened this issue Jun 21, 2022 · 2 comments
Open
Tracked by #50 ...
Assignees
Labels
enhancement New feature or request priority-low Legit issue but cosmetic or nice-to-have

Comments

@JeffinSiby
Copy link

Show Library resources in CICS view

@FALLAI-Denis

We want to use LIBRARY resources in test environments to activate on-demand versions of programs in development:

the CICS test environment works with loadlibs declared in DFHRPL (they could also be declared by LIBRARY resources)
the CICS test environment is permanent and shared by all project teams
each member of a project team compiles (User Build) in a loadlib which is dedicated to the project, (the Db2 objects are common, and the Db2 PLAN contains all the packages, those of the programs in DFHRPL and those of the programs in loadlibs managed in LIBRARY, by playing on the VERSION parameter of Db2 precompilation)
to perform a test, the project team activates its LIBRARY, its programs therefore become active (with a PHASE IN)
at the end of the test, the project team deactivates its LIBRARY, it is the programs in DFHRPL which become active again (with a PHASE IN)
This is a solution that we are currently implementing as part of the switch to CI/CD mode on the mainframe.
This addresses the need to test User Builds triggered from a feature or hotfix branch in a Git workflow (Gitflow).

This allows us to save on the number of CICS test environments, while waiting for a solution to virtualize these environments, (probably Wazi Sandbox).

So we need a way to easily ENAble and DISable a LIBRARY resource, or query the status of a LIBRARY resource.

We also need to list the programs contained in a LIBRARY resource (which can consist of several loadlibs) to trigger the PHASE INs.

The declaration of the LIBRARY resource is made in an automated project initialization process, and its deletion is subordinated to the end of life action of the project.

@JeffinSiby JeffinSiby added the enhancement New feature or request label Jun 21, 2022
@Rajpreetgill Rajpreetgill self-assigned this Jun 28, 2022
@Rajpreetgill Rajpreetgill changed the title Provide the ability to view Library resources Provide the ability to view Library datasets Jul 6, 2022
@Rajpreetgill
Copy link

Rajpreetgill commented Jul 6, 2022

Provide functionality which allows users to see relevant datasets associated with a library resource (in the internal cics view).

@Rajpreetgill Rajpreetgill changed the title Provide the ability to view Library datasets Provide the ability to view Library datasets with the dsnsearchpos of the library dataset Jul 6, 2022
@Rajpreetgill Rajpreetgill changed the title Provide the ability to view Library datasets with the dsnsearchpos of the library dataset Provide the ability to view Library datasets Jul 6, 2022
Rajpreetgill referenced this issue in zowe/vscode-extension-for-cics Jul 13, 2022
Signed-off-by: Rajpreetgill <73036580+Rajpreetgill@users.noreply.github.com>
Rajpreetgill referenced this issue in zowe/vscode-extension-for-cics Jul 15, 2022
addition of library resource; fixes #267, #264, #250, #265
@Rajpreetgill Rajpreetgill reopened this Jul 18, 2022
@Rajpreetgill Rajpreetgill changed the title Provide the ability to view Library datasets Provide the ability to view Library datasets (in external to CICS view) Jul 18, 2022
@zFernand0 zFernand0 transferred this issue from zowe/vscode-extension-for-cics Feb 5, 2024
@zFernand0
Copy link
Member

Provide functionality which allows users to see relevant datasets associated with a library resource (in the internal cics view).

This sounds related toprofileLinks:

@zFernand0 zFernand0 added the priority-low Legit issue but cosmetic or nice-to-have label Feb 6, 2024
@zowe-robot zowe-robot moved this from New Issues to Low Priority in Zowe Explorer for VS Code Feb 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority-low Legit issue but cosmetic or nice-to-have
Projects
Status: Low Priority
Development

No branches or pull requests

3 participants