|
REMINDER *Zowe V2 OFFICE HOURS* Notice for Zowe Consumers
Please mark your calendars or reference the OMP / Zowe Calendar for Zowe V2 Office Hours: https://lists.openmainframeproject.org/g/zowe-dev/calendar The Zowe Onboarding Squad is offering a series of Zowe V2 Office Hours, every Wednesday at 12pm ET throughout the month of April. These webinars will focus on Zowe V2 from a User perspective. Each session will cover a different Zowe component and will include:
Please consider attending this upcoming session focused on Zowe Web UI / Zowe Desktop / App Framework. We look forward to your participation! Did you miss an Office Hours Session? Find prior session recordings and view the schedule here: https://www.zowe.org/vnext#office-hours Best Regards, The Zowe Onboarding Squad Jakub Balhar Michael DuBois Jan Prihoda Rose Sakach Joe Winchester This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it.
|
||||||
|
|
||||||
|
*Zowe V2 OFFICE HOURS* Notice for Zowe Consumers
Please mark your calendars or reference the OMP / Zowe Calendar for Zowe V2 Office Hours: https://lists.openmainframeproject.org/g/zowe-dev/calendar The Zowe Onboarding Squad is offering a series of Zowe V2 Office Hours, every Wednesday at 12pm ET throughout the month of April. These webinars will focus on Zowe V2 from a User perspective. Each session will cover a different Zowe component and will include:
Please consider attending this upcoming session focused on Zowe Explorer (VS Code Extension). We look forward to your participation! Did you miss an Office Hours Session? Find prior session recordings and view the schedule here: https://www.zowe.org/vnext#office-hours Best Regards, The Zowe Onboarding Squad Jakub Balhar Michael DuBois Jan Prihoda Rose Sakach Joe Winchester This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it.
|
||||||
|
|
||||||
|
*ZOWE V2 OFFICE HOURS* Notice for Zowe Consumers
Please mark your calendars or reference the OMP / Zowe Calendar for Zowe V2 Office Hours: https://lists.openmainframeproject.org/g/zowe-dev/calendar The Zowe Onboarding Squad is offering a series of Zowe V2 Office Hours, every Wednesday at 12pm ET throughout the month of April. These webinars will focus on Zowe V2 from a User perspective. Each session will cover a different Zowe component and will include:
Please consider attending this upcoming session focused on Zowe CLI (Command Line Interface). We look forward to your participation! Did you miss an Office Hours Session? Find prior session recordings and view the schedule here: https://www.zowe.org/vnext#office-hours Best Regards, The Zowe Onboarding Squad Jakub Balhar Michael DuBois Jan Prihoda Rose Sakach Joe Winchester This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it.
|
||||||
|
|
||||||
|
*ZOWE V2 OFFICE HOURS* Notice for Zowe Consumers
Please mark your calendars or reference the OMP / Zowe Calendar for Zowe V2 Office Hours: https://lists.openmainframeproject.org/g/zowe-dev/calendar The Zowe Onboarding Squad is offering a series of Zowe V2 Office Hours, every Wednesday at 12pm ET throughout the month of April. These webinars will focus on Zowe V2 from a User perspective. Each session will cover a different Zowe component and will include:
Please consider attending our first session focused on API Mediation Layer. We look forward to your participation! Did you miss an Office Hours Session? Find prior session recordings and view the schedule here: https://www.zowe.org/vnext#office-hours Best Regards, The Zowe Onboarding Squad Jakub Balhar Michael DuBois Jan Prihoda Rose Sakach Joe Winchester This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it.
|
||||||
|
|
||||||
|
test
Thank you, John Mertic Director of Program Management - Linux Foundation Academy Software Foundation, LF Energy, and Open Mainframe Project Schedule a meeting with me at https://meetings.hubspot.com/jmertic
|
||||||
|
|
||||||
|
Re: z/OS 2.5 Compatibility
Jack-Tiefeng Jia
Hi Padmapriya,
We did some test on v2.5 internally and here is what we found.
- We tested Zowe v1.23.0+ on z/OS v2.5 and we don’t see issues. We didn't go back to test Zowe v1.13.
- There was an issue related to Zowe playbooks running on z/OS 2.5 Fixpack 14. This issue doesn't exist with z/OS 2.5 Fixpack 6, and it disappeared on z/OS 2.5 Fixpack 18 on one of the system but still exist on another system. This failure does not affect Zowe runtime but only pipeline. So I think it's worthy to try to bring up Zowe v1.13 on z/OS v2.5. Currently we don't expect failures. If you do see something unexpected, please feel free to contact us.
----- Original message -----
|
||||||
|
|
||||||
|
z/OS 2.5 Compatibility
Forwarding your note along to the zowe-user email list. Thank you, John Mertic Director of Program Management - Linux Foundation Academy Software Foundation, LF Energy, Magma, Open Mainframe Project, and SODA Schedule a meeting with me at https://meetings.hubspot.com/jmertic ---------- Forwarded message --------- From: THUMMALAPENTA, Padmapriya <Padmapriya.THUMMALAPENTA@...> Date: Thu, Dec 9, 2021 at 5:31 AM Subject: z/OS 2.5 Compatibility To: info@... <info@...> Hi,
We are running with ZOWE 1.13 and planning to upgrade from z/OS 2.3 to z/OS 2.5 please provide the compatibility details to move to z/OS 2.5.
Thank you.
Warm Regards
This e-mail is sent by Suncorp Group Limited ABN 66 145 290 124 or one of its related entities "Suncorp". Suncorp may be contacted at Level 28, 266 George Street, Brisbane or on 13 11 55 or at suncorp.com.au. The content of this e-mail is the view of the sender or stated author and does not necessarily reflect the view of Suncorp. The content, including attachments, is a confidential communication between Suncorp and the intended recipient. If you are not the intended recipient, any use, interference with, disclosure or copying of this e-mail, including attachments, is unauthorised and expressly prohibited. If you have received this e-mail in error please contact the sender immediately and delete the e-mail and any attachments from your system.
|
||||||
|
|
||||||
|
Notification - Security Vulnerability - Please Read
Mark.Ackert@...
Hello Zowe Users, We were informed of a published vulnerability in NPM dependencies which affected Zowe CLI’s secure-credential-store during the time period of Nov 4th to Nov 5th. If you installed the plugin from npmjs.org during the vulnerable window of time via a direct command line install, you should follow the recommended resolution steps from the security advisory here: https://github.com/advisories/GHSA-g2q5-5433-rhrf. You are not affected if you downloaded the secure credential store plugin from zowe.org or a Zowe support conformant vendor (IBM or Broadcom). You are not affected if you downloaded from any source prior to Nov 4. The following component versions were affected: @zowe/secure-credential-store-for-zowe-cli@zowe-v1-lts @zowe/secure-credential-store-for-zowe-cli@latest If you issued one of these commands Nov 4 or Nov 5, you should follow the above resolution steps: “zowe plugins install @zowe/secure-credential-store-for-zowe-cli@zowe-v1-lts” “zowe plugins install @zowe/secure-credential-store-for-zowe-cli@latest” Hello Zowe Developers, We found additional Zowe components which the above vulnerability affects at development time, during the same time period of Nov 4th - Nov 5th. There was a second hijacked dependency, https://github.com/veged/coa/issues/99, which contained the same exploit. Conditions for vulnerability:
Thank you This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it.
|
||||||
|
|
||||||
|
Re: How to download files with a "#" in file name
Ajit Sahu
Thank you Very much Joe . Will go through the IBM API doc and get back .
While I am able to get into https://<host>:port , I am yet to get into the whole member GET . I will try it and see what happens . Thanks,Ajit
|
||||||
|
|
||||||
|
Re: How to download files with a "#" in file name
Joe Winchester
Hi Ahit,
The Zowe CLI is backed by z/OSMF REST APIs, and it might be good to try and issue a REST API command directly to see if where the error is being thrown.
The REST API documentation is at https://www.ibm.com/docs/en/zos/2.2.0?topic=interface-retrieve-contents-zos-data-set-member for the z/OSMF REST API used to retrieve a PDS member contents, and an example API would look something like https://<host>:<port>/zosmf/restfiles/ds/HLQ.PDS(MEMBER). I tend to use postman which is a great tool to test REST API requests and responses, although there are other great REST API explorers such as restlet client.
Are you able to construct a raw REST API request to get the contents ?
If you need to reach out to the Zowe CLI squad members themselves a good idea might be to use the slack workspace https://openmainframeproeject.slack.org/ channel #zowe-cli. if this is your first time to sign up to the workspace us the link https://slack.openmainframeproject.org/.
Best regards,
Joe Winchester
Zowe.org Leadership Committee Member - IBM Senior Technical Staff Member - Open Mainframe Project Ambassador
Phone: 44-7749-965423
Twitter: @JoeWinchester LinkedIn: joewinchester
E-mail: winchest@... ----- Original message ----- Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
|
||||||
|
|
||||||
|
Re: How to download files with a "#" in file name
Ajit Sahu
Thank you .I tried ,but still not working for me .tried using the below as well as specifying base path and/or user/Pwd ..still same error .
toggle quoted messageShow quoted text
On Jul 26, 2021, at 5:07 AM, Frans Beyl <frans.beyl@...> wrote:
|
||||||
|
|
||||||
|
Re: How to download files with a "#" in file name
Frans Beyl
The command is the same as you tried but I don't go by API mediation layer, I use zosmf directly with url and port.. zowe zos-files download all-members "datasetname" -H “url zosmf” -P “port zosmf”
node --version v14.15.4 npm --version 6.14.10 zowe --version 6.31.1 Frans Op ma 26 jul. 2021 om 08:22 schreef Ajit Sahu via lists.openmainframeproject.org <ajit.rsahu=icloud.com@...>:
|
||||||
|
|
||||||
|
Re: How to download files with a "#" in file name
Ajit Sahu
Could you please share ,how you did it and what command you used
toggle quoted messageShow quoted text
Ajit
On Jul 25, 2021, at 11:13 PM, Frans Beyl <frans.beyl@...> wrote:
|
||||||
|
|
||||||
|
Re: How to download files with a "#" in file name
Frans Beyl
But then I don't use ml, you might try without it. Op za 24 jul. 2021 om 19:53 schreef Frans Beyl <frans.beyl@...>
|
||||||
|
|
||||||
|
Re: How to download files with a "#" in file name
Frans Beyl
Strange, I just tested and download is fine for all members also one starting with # Op vr 23 jul. 2021 om 18:08 schreef ajit.rsahu via lists.openmainframeproject.org <ajit.rsahu=icloud.com@...>
Thank you Very much Dan for looking into this . I tried your command as well. But its failing with same error.
|
||||||
|
|
||||||
|
Re: How to download files with a "#" in file name
Ajit Sahu
Thank you Very much Dan for looking into this . I tried your command as well. But its failing with same error.
My Command : zowe zos-files download all-members "DatasetName" -b -d "DirectoryLocation" Error Message : z/OSMF REST API Error:
Rest API failure with HTTP(S) status 404
category: 1
rc: 4
reason: 3
message: DatasetName(
Error Details:
HTTP(S) error status "404" received.
Review request details (resource, base path, credentials, payload) and ensure correctness.
Protocol: https
Host: host
Port: port
Base Path: basepath
Resource: /zosmf/restfiles/ds/DatasetName(member1)
Request: GET
Headers: [{"X-IBM-Data-Type":"binary"},{"Accept-Encoding":"gzip"},{"X-IBM-Response-Timeout":"500"},{"X-CSRF-ZOSMF-HEADER":true}]
Payload: undefined Thanks, Ajit
|
||||||
|
|
||||||
|
Re: How to download files with a "#" in file name
Daniel Kelosky
Hi Ajit -
This works in a quick test: `zowe files download ds "ibmuser.work.jcl(#file)"` Can you log your issue here? https://github.com/zowe/zowe-cli/issues Can you paste there the command you ran and the command error output along with the version of zowe CLI you are using (zowe --version)? Thanks, Dan This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it.
|
||||||
|
|
||||||
|
How to download files with a "#" in file name
Ajit Sahu
Hi Team ,
I am trying to download some files using zowe CLI . However, my command failing as some of my file names either start with "#" or contain "#" . Is there any way to download files which has a "#" in the file name . Thanks,Ajit
|
||||||
|
|
||||||
|
Re: Zowe Help for installation on LPAR4
Sean Grady
Hi Fabio.
Yes, having empty folders there is going to cause problems. I saw this once before and I think it was because a user used a pax archive, but had either missing environment variables or missing flags, maybe both.
For all downloads, make sure you have "_BPKX_AUTOCVT=on" in your environment. You could do this manually by "export _BPKX_AUTOCVT=on" in a shell or in the .profile file in your users home directory to have that option persist. Its used to handle file tagging.
For a pax download, make sure to do
pax -ppx -rf zowe-archive-name.pax
Which will extract it into the folder you are in.
If those two tips dont result in having all files there & correct, then I bet there will be some output from the unpax or zowe-install.sh steps that would be useful for us to see in order to know the reason why files are missing.
As for the desktop, in your zowe instance folder, check for the logs directory, which will have appServer log files. Within, you may see an error "ZWED0171W". If you do, it means the desktop is breaking due to a security policy that needs configuration. Just
take whatever hosts or ips you use in your browser to get to the desktop, and enter this into instance.env file:
ZWE_REFERRER_HOSTS=myip,myhost,myip2
It can be a whole list, if your system is accessible in more than one way. We try to capture a series of defaults, but sometimes this explicit configuration is needed. The change would be seen after restarting zowe.
Sean Grady Senior Software Architect Rocket Software 77 Fourth Avenue • Waltham, MA, 02451-1466 • USA t: +1 781 684 2022 • e: sgrady@... • w: www.rocketsoftware.com
From: zowe-user@... <zowe-user@...> on behalf of Fabio Andres Carmona via lists.openmainframeproject.org
<fcarmona=gbm.net@...>
Sent: Monday, June 21, 2021 6:56 PM To: Zowe-user@... <Zowe-user@...> Subject: [zowe-user] Zowe Help for installation on LPAR4
Good morning ZOWE team,
I´m having some problems in my installation of ZOWE 1.19.0, first I ran all scripts from the convenience build successfully. When I tried to verify the access to the ZOWE DESKTOP url: https://myhost:httpsPort, I check that I could get the page, but I got this problem of authentication: Later, when I tried to verify the access to the API Mediation Layer url: https://myhost:gatewayPort/api/v1/apicatalog/application/health, I couldn´t reach the page, I got the following:
After looking through many troubleshooting, I changed my default authenticator from “SAF” to “ZSS”, followings all the steps mentioned in https://docs.zowe.org/stable/user-guide/mvd-configuration.html#multi-factor-authentication-configuration. With this change made, I could access to zowe desktop but some of the plugins weren´t running, other have some issues with permission denied, this is an example, i got this messages:
During my investigation I found that the following address space weren´t running, and the respective ports weren´t listening:
Looking in my installation logs and many troubleshooting and issues from GITHUB and SLACK, I found that folders in <RUNTIME_DIR>/components were empty, look this picture: So I decided, to begin a new installation of ZOWE 1.20.1, in this case I used workflows to complete all configurations. But in this opportunity I checked in the step were the runtime folder its created, to verify the folders from the component folder, and again some of them were empty. So, I downloaded to my computer the ZIP files from installation folder (api-catalog,apiml-common-lib, caching-service, discovery, gateway and jobs-api folders), next I unzipped those folders and copied them back, via FTP, to the component folders of the ZOWE 1.20.1. And then, I continued all the process of the installation. When finished, I tried again to reach the below links, to verify the installation: ZOWE DESKTOP url: https://myhost:httpsPort à Successful with Authorizathor “ZSS” API Mediation Layer url: https://myhost:gatewayPort/api/v1/apicatalog/application/healthàUNSucessful In this new installation, the following address spaces didn´t started:
I verified in the instance.env and check that all parameters where OK, the LAUNCH_COMPONENT_GROUP=DESKTOP,GATEWAY, were verified. All the range from 8542-8550, 7552-7555, 22,23,443 were open to the firewall. My Hostname is: “”icetel4.ice.go.cr”” Here you will find attached the installation log, zssServer log and appServer log from the ZOWE 1.19.1 and ZOWE-1.20.1 installation, for you can check them. IF you need further information, we’ll be a pleasure to send it to you. If you can notice something that I went wrong, or may be some tips and tricks I will appreciate all kind of help. Best Regards. Fabio A. Carmona Rojas COE Z Enginner
================================
|
||||||
|
|
||||||
|
Zowe Help for installation on LPAR4
Fabio Andres Carmona
Good morning ZOWE team,
I´m having some problems in my installation of ZOWE 1.19.0, first I ran all scripts from the convenience build successfully. When I tried to verify the access to the ZOWE DESKTOP url: https://myhost:httpsPort, I check that I could get the page, but I got this problem of authentication: Later, when I tried to verify the access to the API Mediation Layer url: https://myhost:gatewayPort/api/v1/apicatalog/application/health, I couldn´t reach the page, I got the following:
After looking through many troubleshooting, I changed my default authenticator from “SAF” to “ZSS”, followings all the steps mentioned in https://docs.zowe.org/stable/user-guide/mvd-configuration.html#multi-factor-authentication-configuration. With this change made, I could access to zowe desktop but some of the plugins weren´t running, other have some issues with permission denied, this is an example, i got this messages:
During my investigation I found that the following address space weren´t running, and the respective ports weren´t listening:
Looking in my installation logs and many troubleshooting and issues from GITHUB and SLACK, I found that folders in <RUNTIME_DIR>/components were empty, look this picture:
So I decided, to begin a new installation of ZOWE 1.20.1, in this case I used workflows to complete all configurations. But in this opportunity I checked in the step were the runtime folder its created, to verify the folders from the component folder, and again some of them were empty. So, I downloaded to my computer the ZIP files from installation folder (api-catalog,apiml-common-lib, caching-service, discovery, gateway and jobs-api folders), next I unzipped those folders and copied them back, via FTP, to the component folders of the ZOWE 1.20.1. And then, I continued all the process of the installation. When finished, I tried again to reach the below links, to verify the installation: ZOWE DESKTOP url: https://myhost:httpsPort à Successful with Authorizathor “ZSS” API Mediation Layer url: https://myhost:gatewayPort/api/v1/apicatalog/application/healthàUNSucessful In this new installation, the following address spaces didn´t started:
I verified in the instance.env and check that all parameters where OK, the LAUNCH_COMPONENT_GROUP=DESKTOP,GATEWAY, were verified. All the range from 8542-8550, 7552-7555, 22,23,443 were open to the firewall. My Hostname is: “”icetel4.ice.go.cr”” Here you will find attached the installation log, zssServer log and appServer log from the ZOWE 1.19.1 and ZOWE-1.20.1 installation, for you can check them. IF you need further information, we’ll be a pleasure to send it to you. If you can notice something that I went wrong, or may be some tips and tricks I will appreciate all kind of help. Best Regards. Fabio A. Carmona Rojas COE Z Enginner
|
||||||
|
|
||||||
