|
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
|
||
|
|
||
|
Re: zowe extension problems
Joe Winchester
Hi Richard,
>..I've trying to create a zowe profile in vs code and I get a response that says there is a problem with the zowe extension. I'm stuck
Can you post a screen shot of the error you're getting ?
The youtube video https://www.youtube.com/watch?v=G_WCsFZIWt4 shows how to get started with the Zowe Explorer.
Are you able to use slack ? If you can register for the open mainframe slack channel at https://slack.openmainframeproject.org/ and there is a dedicated channel #zowe-explorer where you should be able to get help from the community.
Best regards,
Joe Winchester
Project Zowe Leadership Committee member zowe.org - IBM Senior Technical Staff Member and Zowe architect
Phone: 44-7749-965423
Twitter: @JoeWinchester LinkedIn: joewinchester
E-mail: winchest@... ----- Original message ----- IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
|
||
|
|
||
|
Re: zowe extension problems
Michael Erichsen <michael.erichsen@...>
Hi Richard
Can you share some more details on what you have done, and the exact error messages?
Med venlig hilsen/Best regards
Michael Erichsen
Xact Consulting A/S Tlf.: +45 70 23 01 00
Mobil/Cell: +45 23 10 33 85 LinkedIn: https://www.linkedin.com/in/michaelerichsen/ Slideshare: https://www.slideshare.net/dsmer Youtube: https://www.youtube.com/user/MichaelErichsen Web: www.xact.dk Private mail: michael@...
Early notification of permanent absence: After September 30th, 2020
From: zowe-user@... <zowe-user@...>
On Behalf Of John Mertic via lists.openmainframeproject.org
Sent: 29. juni 2020 14:31 To: Richard Ricciardi <rickster66@...>; zowe-user@... Cc: Open Mainframe Project <info@...> Subject: Re: [zowe-user] zowe extension problems
On Sat, Jun 27, 2020 12:51 AM, Richard Ricciardi rickster66@... wrote:
|
||
|
|
||
|
Re: zowe extension problems
On Sat, Jun 27, 2020 12:51 AM, Richard Ricciardi rickster66@... wrote:
|
||
|
|
||
|
Re: ZOWE on ZD&T (was Follow up to Membership Inquiry with the Open Mainframe Project)
Matt Hogstrom
WRT to ZD&T.
toggle quoted messageShow quoted text
As a platform it is a priced platform from IBM that runs on Intel and emulates the IBM Z instruction set as well as abstracts I/O. In general it is used as a low-cost alternative to owning an actual Z platform and is primarily targeted at test / development environments. As part of the Terms and Conditions of ZD&T binaries produced on that emulated environment cannot be distributed for execution on real-Z hardware deployments. Its not that the binaries are not the same, its simply a set of terms and conditions. Please review the IBM Terms and Conditions to verify the current ones as I’m sure they’ll be changing over time. Here is a link to V12 (I’m not sure what is the current version) https://www.ibm.com/support/knowledgecenter/SSTQBD_12.0.1/com.ibm.zdt.overview.gs.doc/topics/c_product_overview.html And a disclaimer for that version  Here is a link to the Development Platform https://www.ibm.com/developerworks/community/forums/html/topic?id=b824cabc-a0fa-4ea0-b45f-54f05d099b28 Zowe does use ZD&T as part of its verification pipeline as provided by donors outside the OMP. Currently the OMP does not manage or provide access to ZD&T licenses. With that as a preamble Java seems to perform poorly on ZD&T. I don’t know the reason for that but I’ve heard a number of speculations but never any real data. That said, it has little to do with z/OSMF apart from it using Java as its primary operating environment. Other interfaces that Zowe interfaces with like the Explorer runtime as well as API Mediation layer also use Java. The primary difference between their use and z/OSMF is that z/OSMF is much more tightly tied into the z/OS operating system and is a strategic delivery for services on z/OS. API ML and z/OS Explorer both use z/OSMF services. There are plans to build new functionality to limit or replace the dependence on z/OSMF and provide new means of delivering the capabilities. Bear in mind that z/OSMF is a collection of services and not a “thing.” Here is a list of z/OSMF services: •z/OS data set and file REST services - Supports working with z/OS data sets, Unix files and Unix directories such as create data set, read/write content of data sets, query data sets, query Unix files, etc. •z/OS jobs REST services - Supports working with z/OS jobs such as list jobs according to specified criteria, submit job, retrieve job spool files, purge job, etc. •z/OS console services - Supports working with z/OS console such as issue console command, retrieve command response, monitor console messages for specified keywords, etc. •TSO/E address space services - Supports working with z/OS TSO address space such as start TSO/E address space, start a TSO application, issue TSO command, etc. •Notification services - Supports working with notifications such as send a mail/mobile notification, retrieve all notification received, etc. •Cloud Provisioning services - Supports provisioning MWs like DB2, CICS, IMS, MQ, WebSphere via REST APIs. •Workflow services - Supports working with z/OSMF workflow via REST APIs such as creating a workflow, starting a workflow, cancel a workflow, etc. •Software Management services - Supports working with z/OS Software via REST APIs such as add a software instance, export a software instance, retrieve properties of software, etc. •Application Linking Manager services - Allows 3rd party application to integrate with z/OSMF applications via REST APIs such as registering event which could be handled by z/OSMF application or register itself as a handler to handle z/OSMF events, etc. •Topology services - Supports retrieving topology information managed by z/OSMF Systems task via REST APIs. •Application server routing services - Supports route your UI requests to a separate application server when you develop an external z/OSMF application. As Zowe chooses to move away from z/OSMF (if that is the strategic strategy by the project) all of these functions (if needed by Zowe applications) will have to be re-written in new ways and maintained by the community. My experience is that z/OSMF when tuned does take about 16 minutes to initialize on my ZD&T system but performs well once initialized. I’m not advocating for one position or another (although my personal opinion is that Zowe should be engaging more actively with IBM z/OSMF team rather than rewrite function that is already delivered as part of the platform). Rather than using the term z/OSMF I think the more productive conversation is to discuss the services needed, the challenges and issues encountered than to simply generalize the conversation and take on a boatload of additional work that doesn’t make Zowe stronger, it puts it in a weaker position because they are competing against IBM development rather than complimenting and extending.
|
||
|
|
||
|
Re: ZOWE on ZD&T (was Follow up to Membership Inquiry with the Open Mainframe Project)
sebastian@...
I have installed and run it successfully on zPDT and ZD&T although it wasn't an easy experience. Originally performance was quite slow but tuning of zOSMF helped and I suspect further Java tuning would also help. I also have customers now starting to use it on these platforms.
When I was doing it, I did come across the following 2 statements regarding it on these platforms:
Followed by:
MfG / Best Regards --- Sebastian Welton | Managing Director for EMEA Support | zSystems, Linux and Cloud
|
||
|
|
||
|
Re: Follow up to Membership Inquiry with the Open Mainframe Project
Michael Erichsen <michael.erichsen@...>
Hi
I have worked on installing Zowe on ZD&T. It kept on timing out, probably due to ZOSMF overhead, even though I ran with 4 normal CPU’s, three Ziips and a cryptocoprocessor. The upcoming V1.8 should be without ZOSMF, so I am waiting for that before trying again.
Med venlig hilsen/Best regards
Michael Erichsen
Tlf.: +45 70 23 01 00
Mobil/Cell: +45 23 10 33 85 LinkedIn: https://www.linkedin.com/in/michaelerichsen/ Slideshare: https://www.slideshare.net/dsmer Youtube: https://www.youtube.com/user/MichaelErichsen Web: www.xact.dk
Early notification of absence: None
From: zowe-user@... <zowe-user@...>
On Behalf Of John Mertic via Lists.Openmainframeproject.Org
Sent: 2. marts 2020 14:34 To: Angelin Mariya <angelin.mariya@...>; zowe-user@... Cc: John Mertic <jmertic@...> Subject: Re: [zowe-user] Follow up to Membership Inquiry with the Open Mainframe Project
Appreciate your note. I'd suggest posting this question to the zowe-user email list - I'll CCed this now.
Thank you,
John Mertic Director of Program Management - Linux Foundation ASWF, ODPi, and Open Mainframe Project Schedule time with me at https://calendly.com/jmertic
On Mon, Mar 2, 2020 at 8:04 AM Angelin Mariya <angelin.mariya@...> wrote:
|
||
|
|
||
|
Re: Follow up to Membership Inquiry with the Open Mainframe Project
Appreciate your note. I'd suggest posting this question to the zowe-user email list - I'll CCed this now. Thank you, John Mertic Director of Program Management - Linux Foundation ASWF, ODPi, and Open Mainframe Project
On Mon, Mar 2, 2020 at 8:04 AM Angelin Mariya <angelin.mariya@...> wrote:
|
||
|
|
||
|
Re: NOMINATIONS RESULT: ZLC Voting seat
Wu Song IF Fang
Congratulations, Joe!
Best Regards, Wusong Fang (方吾松) Email : bjwsfang@... Tel : (86-10)8245 1195 Address: 28, ZhongGuanCun Software Park, No.8 Dong Bei Wang West Road, Haidian District Beijing P.R.China 100193 地址 ：北京市海淀区东北旺西路8号中关村软件园28号环宇大厦 邮编：100193
----- Original message -----
|
||
|
|
