Re: AZD messages?
gets a zero condition code doesn’t mean it executed > successfully. > >> You have to check STDERR and STDOUT tabs. Mine always gets a syntax > >> error. > >> > >> On Thu, Jun 4, 2020 at 10:05 AM Sean Gleann > wrote: > >> > >>> It's been really quite a troublesome effort for me, Michael, but I > guess > >>> it's true to say that most of the problems are down to my rudimentary > >>> knowledge of TCPIP and networking in general. > >>> For various reasons, I have to use a tunnelled connection through to > the > >>> z/OS guest, and that makes things a bit more interesting. > >>> The 'Getting Started' redbook (SG24-8457-00) has been my sole point of > >>> reference all the way through, and yeah, it's OK - up to point. it > >> doesn't > >>> cover the tunnelling complication, naturally, and there are some very > >> poor > >>> typos to take into account. > >>> As for the Workload Provisioning process in z/OSMF - after you've > >> specified > >>> a bunch of parameters, it's just a JCL generator/job submitter/checker > >> with > >>> a couple of z/OSMF-specific bits thrown in. > >>> During the initial parameter specification phase I had considerable > >>> difficulty at the point of specifying the RSA key, but eventually got > it > >>> right. > >>> Step 3.2 in the process - where some sort of version information is > >> looked > >>> for - has always failed for me. I've never been able to make it work as > >>> expected and have had to force it to a 'complete' state by clicking the > >>> 'Finish' button. > >>> > >>> I tried to adapt the process detailed in the redbook to suit our > security > >>> set-up, but the result never worked. In the end, I followed the > procedure > >>> to the letter, and created the ZCXxxx users and groups in RACF as > >>> specified. > >>> Result - I've finally got a working container that I can log in to. The > >>> next step according to the redbook is to download an image from > >>> hub.docker.com, but when I try the specified command - 'docker pull > >> nginx' > >>> - the container tries to go to registry-1.docker/.io/v2 - which isn't > >>> specified anywhere in the parameter files created by z/OSMF - and it > >> times > >>> out. > >>> I've added suitable mods to \etc\hosts, \etc\ipnodes and to > TCPIP.HOSTS, > >>> messed around with DNS specifications and I've commented out the IPSEC > >>> statements in the TCPIP PROFILE parameters (thank gawd for sandbox > >>> systems!). Nothing along those lines has altered the situation. > >>> Now, I'm waiting for our company networking guys to suggest other > things > >> to > >>> try. > >>> > >>> Good luck with your efforts, Michael. > >>> I hope you have a smoother ride than I have had so far. > >>> > >>> Sean > >>> > >>> On Thu, 4 Jun 2020 at 15:32, Michael Babcock > >>> wrote: > >>> > >>>> Sean, > >>>> > >>>> I’m just going through the provisioning process now. Any gotchas that > >>> you > >>>> care to share? > >>>> > >>>> On Thu, Jun 4, 2020 at 5:30 AM Sean Gleann > >>> wrote: > >>>>> Thanks, Gadi. > >>>>> Yes, there are GLZ messages associated with these AZDs, but all they > >> do > >>>> is > >>>>> identify the stored failure data. > >>>>> > >>>>> It's all somewhat moot now. I tried to /P the container, and got told > >>> the > >>>>> task was non-cancellable. > >>>>> Eventually I resorted to a FORCE ARM to get rid of it. > >>>>> Restarted the task and now it's running perfectly! No errors or > >>> warnings, > >>>>> and I'm logged in, ready to start working with my first container. > >>>>> > >>>>> Sean > >>>>> > >>>>> On Thu, 4 Jun 2020 at 11:12, Gadi Ben-Avi wrote: > >>>>> > >>>>>> I found this: > >>>>>> > >>>>>> > >> > https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.izso100/izso100_diagnosisservice.htm > >>>>>> It looks like the real information is in GLZ messages. >
Re: AZD messages?
Step 3.2 in the process - where some sort of version information is looked for - has always failed for me. I've never been able to make it work as expected and have had to force it to a 'complete' state by clicking the 'Finish' button. I tried to adapt the process detailed in the redbook to suit our security set-up, but the result never worked. In the end, I followed the procedure to the letter, and created the ZCXxxx users and groups in RACF as specified. Result - I've finally got a working container that I can log in to. The next step according to the redbook is to download an image from hub.docker.com, but when I try the specified command - 'docker pull nginx' - the container tries to go to registry-1.docker/.io/v2 - which isn't specified anywhere in the parameter files created by z/OSMF - and it times out. I've added suitable mods to \etc\hosts, \etc\ipnodes and to TCPIP.HOSTS, messed around with DNS specifications and I've commented out the IPSEC statements in the TCPIP PROFILE parameters (thank gawd for sandbox systems!). Nothing along those lines has altered the situation. Now, I'm waiting for our company networking guys to suggest other things to try. Good luck with your efforts, Michael. I hope you have a smoother ride than I have had so far. Sean On Thu, 4 Jun 2020 at 15:32, Michael Babcock wrote: Sean, I’m just going through the provisioning process now. Any gotchas that you care to share? On Thu, Jun 4, 2020 at 5:30 AM Sean Gleann wrote: Thanks, Gadi. Yes, there are GLZ messages associated with these AZDs, but all they do is identify the stored failure data. It's all somewhat moot now. I tried to /P the container, and got told the task was non-cancellable. Eventually I resorted to a FORCE ARM to get rid of it. Restarted the task and now it's running perfectly! No errors or warnings, and I'm logged in, ready to start working with my first container. Sean On Thu, 4 Jun 2020 at 11:12, Gadi Ben-Avi wrote: I found this: https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.izso100/izso100_diagnosisservice.htm It looks like the real information is in GLZ messages. I don't have z/OS v2.4 running, so I can't really check. Gadi -Original Message- From: IBM Mainframe Discussion List On Behalf Of Sean Gleann Sent: Thursday, June 4, 2020 12:53 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: AZD messages? Can anyone point me at documentation for AZD... messages coming out of a zcx container, please? I'm getting: AZDN0004E Failure configuring IPv4 address and AZDP0001E Unexpected error 5 configuring data disks but various attempts at searching for these produce 'nothing found' responses. Regards Sean -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Email secured by Check Point -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Michael Babcock OneMain Financial z/OS Systems Programmer, Lead -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Michael Babcock OneMain Financial z/OS Systems Programmer, Lead -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: AZD messages?
HTTPS and not HTTP >> 2. Check for TLS1.2 - lower levels of SSL / TLS are often not allowed >> these days >> 3. Check the ZOSMF server certificate Is signed by a CA trusted by Opera >> 4. Check certificate dates >> 5. Confirm the DNS you used to reach ZOSMF is named as a subject >> alternate name >> >> Browsers have an icon to click showing why a connection is not secure. It >> will very likely be one of the steps above. >> >> Some browsers allow you to allow connections with an untrusted >> certificate. That would be a bad security practice but may allow an initial >> connection. >> >> Hope some of this helps. It is generic advice for any browser connection >> to z/OS. >> >> Mike Wawiorko >> >> >> -Original Message- >> From: IBM Mainframe Discussion List On Behalf >> Of Sean Gleann >> Sent: 08 June 2020 14:15 >> To: IBM-MAIN@LISTSERV.UA.EDU >> Subject: Re: AZD messages? >> >> >> This message originated from outside our organisation and is from web >> based email - sean.gle...@gmail.com >> >> As far as I understand things, 'localhost' is just another way of saying >> '127.0.0.1' meaning 'this computer', so - yes, localhost is defined. >> I have an SSH connection defined in PuTTY that associates my local 10443 >> with the host system's 10443, and I start that connection before attempting >> to go to https://localhost:10443 in my browser (Opera). >> I'm quite happy to be shown any error in my understanding, however. >> >> But you've sparked off another train of thought, Lloyd. >> Whilst it's true I get to my z/OSMF with 'https://localhost:10443/zosmf', >> the very first thing I see is a warning that the connection is not secure >> and I have to click on 'continue anyway' in order to get to the z/OSMF >> sign-on screen. >> I think I've got to sort out *that* problem before trying to go any >> further. >> >> Regards >> Sean >> >> , >> >> >> This e-mail and any attachments are confidential and intended solely for >> the addressee and may also be privileged or exempt from disclosure under >> applicable law. If you are not the addressee, or have received this e-mail >> in error, please notify the sender immediately, delete it from your system >> and do not copy, disclose or otherwise act upon any part of this e-mail or >> its attachments. >> Internet communications are not guaranteed to be secure or virus-free. >> The Barclays Group does not accept responsibility for any loss arising from >> unauthorised access to, or interference with, any Internet communications >> by any third party, or from the transmission of any viruses. Replies to >> this e-mail may be monitored by the Barclays Group for operational or >> business reasons. >> Any opinion or other information in this e-mail or its attachments that >> does not relate to the business of the Barclays Group is personal to the >> sender and is not given or endorsed by the Barclays Group. >> Barclays Execution Services Limited provides support and administrative >> services across Barclays group. Barclays Execution Services Limited is an >> appointed representative of Barclays Bank UK plc, Barclays Bank plc and >> Clydesdale Financial Services Limited. Barclays Bank UK plc and Barclays >> Bank plc are authorised by the Prudential Regulation Authority and >> regulated by the Financial Conduct Authority and the Prudential Regulation >> Authority. Clydesdale Financial Services Limited is authorised and >> regulated by the Financial Conduct Authority. >> >> -- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >> > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: AZD messages?
Thank you Dave - I was unaware of that qualification. Checked and, yes, 'localhost' is defined in my RESOLVER parameters Sean On Mon, 8 Jun 2020 at 17:33, Mike Wawiorko < 014ab5cdfb21-dmarc-requ...@listserv.ua.edu> wrote: > I hope I'm understanding what you are saying. > > Localhost is for use ONLY within a single TCPIP stack or system. It is > another way of writing non-routable IP address '127.0.0.1'. > Maybe configuring host files will allow you to do this but that will be > very confusing and awkward to support. > > You should NOT be using localhost to get from your device (PC or whatever) > to the z/OS TCPIP stack. > > You should configure a name for your ZOSMF IP address. > If you always run ZOSMF on the same z/OS system you may already have a > suitable name in DNS for the system's static VIPA. > If you move ZOSMF between systems in the sysplex you will need a Dynamic > Virtual IP Address (DVIPA) and an entry in DNS (or host files) for it. > > I'm struggling to follow what you are saying about PuTTY for SSH and your > Opera browser. > > You might use your SSH connection to get to z/OS and work with USS and > perform some configuration actions. You do not use PuTTY to logon to ZOSMF. > > You should have a ZOSMF server certificate signed by a CA trusted by your > browser. > This certificate should - probably must - include the DNS name as a > subject alternate name. > > When you make the HTTPS connection from the browser Opera will validate > the security of the connection. That will include: > 1. Check that it is indeed HTTPS and not HTTP > 2. Check for TLS1.2 - lower levels of SSL / TLS are often not allowed > these days > 3. Check the ZOSMF server certificate Is signed by a CA trusted by Opera > 4. Check certificate dates > 5. Confirm the DNS you used to reach ZOSMF is named as a subject alternate > name > > Browsers have an icon to click showing why a connection is not secure. It > will very likely be one of the steps above. > > Some browsers allow you to allow connections with an untrusted > certificate. That would be a bad security practice but may allow an initial > connection. > > Hope some of this helps. It is generic advice for any browser connection > to z/OS. > > Mike Wawiorko > > > -Original Message- > From: IBM Mainframe Discussion List On Behalf > Of Sean Gleann > Sent: 08 June 2020 14:15 > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: AZD messages? > > > This message originated from outside our organisation and is from web > based email - sean.gle...@gmail.com > > As far as I understand things, 'localhost' is just another way of saying > '127.0.0.1' meaning 'this computer', so - yes, localhost is defined. > I have an SSH connection defined in PuTTY that associates my local 10443 > with the host system's 10443, and I start that connection before attempting > to go to https://localhost:10443 in my browser (Opera). > I'm quite happy to be shown any error in my understanding, however. > > But you've sparked off another train of thought, Lloyd. > Whilst it's true I get to my z/OSMF with 'https://localhost:10443/zosmf', > the very first thing I see is a warning that the connection is not secure > and I have to click on 'continue anyway' in order to get to the z/OSMF > sign-on screen. > I think I've got to sort out *that* problem before trying to go any > further. > > Regards > Sean > > , > > > This e-mail and any attachments are confidential and intended solely for > the addressee and may also be privileged or exempt from disclosure under > applicable law. If you are not the addressee, or have received this e-mail > in error, please notify the sender immediately, delete it from your system > and do not copy, disclose or otherwise act upon any part of this e-mail or > its attachments. > Internet communications are not guaranteed to be secure or virus-free. The > Barclays Group does not accept responsibility for any loss arising from > unauthorised access to, or interference with, any Internet communications > by any third party, or from the transmission of any viruses. Replies to > this e-mail may be monitored by the Barclays Group for operational or > business reasons. > Any opinion or other information in this e-mail or its attachments that > does not relate to the business of the Barclays Group is personal to the > sender and is not given or endorsed by the Barclays Group. > Barclays Execution Services Limited provides support and administrative > services across Barclays group. Barclays Execution Services Limited is an > appointed representative of Barclays Bank UK plc, Barclays Bank plc and > Clydesdale Financial Serv
Re: AZD messages?
I hope I'm understanding what you are saying. Localhost is for use ONLY within a single TCPIP stack or system. It is another way of writing non-routable IP address '127.0.0.1'. Maybe configuring host files will allow you to do this but that will be very confusing and awkward to support. You should NOT be using localhost to get from your device (PC or whatever) to the z/OS TCPIP stack. You should configure a name for your ZOSMF IP address. If you always run ZOSMF on the same z/OS system you may already have a suitable name in DNS for the system's static VIPA. If you move ZOSMF between systems in the sysplex you will need a Dynamic Virtual IP Address (DVIPA) and an entry in DNS (or host files) for it. I'm struggling to follow what you are saying about PuTTY for SSH and your Opera browser. You might use your SSH connection to get to z/OS and work with USS and perform some configuration actions. You do not use PuTTY to logon to ZOSMF. You should have a ZOSMF server certificate signed by a CA trusted by your browser. This certificate should - probably must - include the DNS name as a subject alternate name. When you make the HTTPS connection from the browser Opera will validate the security of the connection. That will include: 1. Check that it is indeed HTTPS and not HTTP 2. Check for TLS1.2 - lower levels of SSL / TLS are often not allowed these days 3. Check the ZOSMF server certificate Is signed by a CA trusted by Opera 4. Check certificate dates 5. Confirm the DNS you used to reach ZOSMF is named as a subject alternate name Browsers have an icon to click showing why a connection is not secure. It will very likely be one of the steps above. Some browsers allow you to allow connections with an untrusted certificate. That would be a bad security practice but may allow an initial connection. Hope some of this helps. It is generic advice for any browser connection to z/OS. Mike Wawiorko -Original Message- From: IBM Mainframe Discussion List On Behalf Of Sean Gleann Sent: 08 June 2020 14:15 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: AZD messages? This message originated from outside our organisation and is from web based email - sean.gle...@gmail.com As far as I understand things, 'localhost' is just another way of saying '127.0.0.1' meaning 'this computer', so - yes, localhost is defined. I have an SSH connection defined in PuTTY that associates my local 10443 with the host system's 10443, and I start that connection before attempting to go to https://localhost:10443 in my browser (Opera). I'm quite happy to be shown any error in my understanding, however. But you've sparked off another train of thought, Lloyd. Whilst it's true I get to my z/OSMF with 'https://localhost:10443/zosmf', the very first thing I see is a warning that the connection is not secure and I have to click on 'continue anyway' in order to get to the z/OSMF sign-on screen. I think I've got to sort out *that* problem before trying to go any further. Regards Sean , This e-mail and any attachments are confidential and intended solely for the addressee and may also be privileged or exempt from disclosure under applicable law. If you are not the addressee, or have received this e-mail in error, please notify the sender immediately, delete it from your system and do not copy, disclose or otherwise act upon any part of this e-mail or its attachments. Internet communications are not guaranteed to be secure or virus-free. The Barclays Group does not accept responsibility for any loss arising from unauthorised access to, or interference with, any Internet communications by any third party, or from the transmission of any viruses. Replies to this e-mail may be monitored by the Barclays Group for operational or business reasons. Any opinion or other information in this e-mail or its attachments that does not relate to the business of the Barclays Group is personal to the sender and is not given or endorsed by the Barclays Group. Barclays Execution Services Limited provides support and administrative services across Barclays group. Barclays Execution Services Limited is an appointed representative of Barclays Bank UK plc, Barclays Bank plc and Clydesdale Financial Services Limited. Barclays Bank UK plc and Barclays Bank plc are authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the Prudential Regulation Authority. Clydesdale Financial Services Limited is authorised and regulated by the Financial Conduct Authority. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: AZD messages?
Only if localsthost is defined as such in the RESOLVER configuration or your DNS systems > -Original Message- > From: IBM Mainframe Discussion List On > Behalf Of Sean Gleann > Sent: Monday, June 08, 2020 6:15 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: AZD messages? > > As far as I understand things, 'localhost' is just another way of saying > '127.0.0.1' meaning 'this computer', so - yes, localhost is defined. > I have an SSH connection defined in PuTTY that associates my local 10443 with > the host system's 10443, and I start that connection before attempting to go > to > https://urldefense.com/v3/__https://localhost:10443__;!!JmPEgBY0HMszNa > DT!8oEEMOEuRoL6eOh5CUG3s4l_6_KEa4iQN03dcleBjVBuDQNXegm7lYxh03c > DuQ$ in my browser (Opera). > I'm quite happy to be shown any error in my understanding, however. > > But you've sparked off another train of thought, Lloyd. > Whilst it's true I get to my z/OSMF with > 'https://urldefense.com/v3/__https://localhost:10443/zosmf__;!!JmPEgBY0 > HMszNaDT!8oEEMOEuRoL6eOh5CUG3s4l_6_KEa4iQN03dcleBjVBuDQNXegm > 7lYzS28lZ8g$ ', the very first thing I see is a warning that the connection > is not > secure and I have to click on 'continue anyway' in order to get to the z/OSMF > sign-on screen. > I think I've got to sort out *that* problem before trying to go any further. > > Regards > Sean > > , > > On Mon, 8 Jun 2020 at 13:55, Lloyd Fuller wrote: > > > Is localhost defined? > > > > Sent from my iPad > > > > > On Jun 8, 2020, at 8:16 AM, Sean Gleann > wrote: > > > > > > Thanks for the hint about thoroughly checking output, Michael. > > > I went back and studied all the saved outputs, hoping to find > > > something that might be helpful. > > > In the event, there were no indications of such problems - no error > > > messages or non-zero return codes - but it's as well to be sure. > > > > > > Can I ask you for more information regarding what you see with the > > > '3.2 Retrieve Workflow version' step, please? > > > For me, I get to the point of clicking 'Perform' on this step, and I > > > see that z/OSMF is about to use the REST API with the request > > > > > > > > > https://urldefense.com/v3/__https://localhost:10443/zosmf/workflow/res > > t/1.0/workflows/3ca56936-9a81-48a0-94d9- > 84e28ee2d842__;!!JmPEgBY0HMszN > > > aDT!8oEEMOEuRoL6eOh5CUG3s4l_6_KEa4iQN03dcleBjVBuDQNXegm7lYwoO > 2GQBg$ > > > : > > > > > > Clicking 'Next' on this results in: > > > > > > IZUWFE: The request cannot be completed because an error > occurred. > > The > > > following error data is returned: "EDC8128I Connection refused. > > > (errno2=0x76630291) (Connection refused)" > > > > > > and so I am forced to click on 'Finish' if I am to proceed. > > > What do you see during this sequence? > > > > > > I suspect that it's the 'localhost:10443' bit that is the root of > > > the problem, but I'm unsure how to circumvent it, or even to correct > > > the problem. > > > As I said earlier in this thread, I'm working through a tunnelled > > > SSH connection to access my z/OSMF. In the main, this is working > > > quite > > happily. > > > That connection definition associates my desktop system's local port > > 10443 > > > with the hosts systems' 10443, and the URL I use to access z/OSMF is > > > > https://urldefense.com/v3/__https://localhost:10443/zosmf__;!!JmPEgBY0 > HMszNaDT!8oEEMOEuRoL6eOh5CUG3s4l_6_KEa4iQN03dcleBjVBuDQNXegm > 7lYzS28lZ8g$ . > > > So I'm at a bit of a loss in understanding why the connection should > > > be refused. > > > > > > Regards > > > Sean > > > > > > > > >> On Fri, 5 Jun 2020 at 04:08, Michael Babcock > > >> > > wrote: > > >> > > >> Oh and beware, just because the Verify Feature Bits job (and a > > >> couple of > > >> others) gets a zero condition code doesn’t mean it executed > > successfully. > > >> You have to check STDERR and STDOUT tabs. Mine always gets a > > >> syntax error. > > >> > > >>> On Thu, Jun 4, 2020 at 10:05 AM Sean Gleann > > >>> > > wrote: > > >>> > > >>> It's been really quite a troublesome effort for me, Michael, but I > > guess > > >>> it's true to say that most of the problems are down to my > > >>> rudimentary knowledge of TCPIP and network
Re: AZD messages?
ied to adapt the process detailed in the redbook to suit our > security > >>> set-up, but the result never worked. In the end, I followed the > procedure > >>> to the letter, and created the ZCXxxx users and groups in RACF as > >>> specified. > >>> Result - I've finally got a working container that I can log in to. The > >>> next step according to the redbook is to download an image from > >>> hub.docker.com, but when I try the specified command - 'docker pull > >> nginx' > >>> - the container tries to go to registry-1.docker/.io/v2 - which isn't > >>> specified anywhere in the parameter files created by z/OSMF - and it > >> times > >>> out. > >>> I've added suitable mods to \etc\hosts, \etc\ipnodes and to > TCPIP.HOSTS, > >>> messed around with DNS specifications and I've commented out the IPSEC > >>> statements in the TCPIP PROFILE parameters (thank gawd for sandbox > >>> systems!). Nothing along those lines has altered the situation. > >>> Now, I'm waiting for our company networking guys to suggest other > things > >> to > >>> try. > >>> > >>> Good luck with your efforts, Michael. > >>> I hope you have a smoother ride than I have had so far. > >>> > >>> Sean > >>> > >>> On Thu, 4 Jun 2020 at 15:32, Michael Babcock > >>> wrote: > >>> > >>>> Sean, > >>>> > >>>> I’m just going through the provisioning process now. Any gotchas that > >>> you > >>>> care to share? > >>>> > >>>> On Thu, Jun 4, 2020 at 5:30 AM Sean Gleann > >>> wrote: > >>>> > >>>>> Thanks, Gadi. > >>>>> Yes, there are GLZ messages associated with these AZDs, but all they > >> do > >>>> is > >>>>> identify the stored failure data. > >>>>> > >>>>> It's all somewhat moot now. I tried to /P the container, and got told > >>> the > >>>>> task was non-cancellable. > >>>>> Eventually I resorted to a FORCE ARM to get rid of it. > >>>>> Restarted the task and now it's running perfectly! No errors or > >>> warnings, > >>>>> and I'm logged in, ready to start working with my first container. > >>>>> > >>>>> Sean > >>>>> > >>>>> On Thu, 4 Jun 2020 at 11:12, Gadi Ben-Avi wrote: > >>>>> > >>>>>> I found this: > >>>>>> > >>>>>> > >>>>> > >>>> > >>> > >> > https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.izso100/izso100_diagnosisservice.htm > >>>>>> > >>>>>> It looks like the real information is in GLZ messages. > >>>>>> > >>>>>> I don't have z/OS v2.4 running, so I can't really check. > >>>>>> > >>>>>> Gadi > >>>>>> > >>>>>> -Original Message- > >>>>>> From: IBM Mainframe Discussion List On > >>>> Behalf > >>>>>> Of Sean Gleann > >>>>>> Sent: Thursday, June 4, 2020 12:53 PM > >>>>>> To: IBM-MAIN@LISTSERV.UA.EDU > >>>>>> Subject: AZD messages? > >>>>>> > >>>>>> Can anyone point me at documentation for AZD... messages coming out > >>> of > >>>> a > >>>>>> zcx container, please? > >>>>>> > >>>>>> I'm getting: > >>>>>> AZDN0004E Failure configuring IPv4 address and AZDP0001E > >>>> Unexpected > >>>>>> error 5 configuring data disks > >>>>>> > >>>>>> but various attempts at searching for these produce 'nothing found' > >>>>>> responses. > >>>>>> > >>>>>> Regards > >>>>>> Sean > >>>>>> > >>>>>> > >>> -- > >>>>>> For IBM-MAIN subscribe / signoff / archive access instructions, > >> send > >>>>> email > >>>>>> to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > >>>>>> > >>>>>> Email secured by Check Point > >>>>>> > >>>>>> > >>> -- > >>>>>> For IBM-MAIN subscribe / signoff / archive access instructions, > >>>>>> send email to lists...@listserv.ua.edu with the message: INFO > >>> IBM-MAIN > >>>>>> > >>>>> > >>>>> > >> -- > >>>>> For IBM-MAIN subscribe / signoff / archive access instructions, > >>>>> send email to lists...@listserv.ua.edu with the message: INFO > >> IBM-MAIN > >>>>> > >>>> -- > >>>> Michael Babcock > >>>> OneMain Financial > >>>> z/OS Systems Programmer, Lead > >>>> > >>>> -- > >>>> For IBM-MAIN subscribe / signoff / archive access instructions, > >>>> send email to lists...@listserv.ua.edu with the message: INFO > IBM-MAIN > >>>> > >>> > >>> -- > >>> For IBM-MAIN subscribe / signoff / archive access instructions, > >>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > >>> > >> -- > >> Michael Babcock > >> OneMain Financial > >> z/OS Systems Programmer, Lead > >> > >> -- > >> For IBM-MAIN subscribe / signoff / archive access instructions, > >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > >> > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: AZD messages?
had so far. >>> >>> Sean >>> >>> On Thu, 4 Jun 2020 at 15:32, Michael Babcock >>> wrote: >>> >>>> Sean, >>>> >>>> I’m just going through the provisioning process now. Any gotchas that >>> you >>>> care to share? >>>> >>>> On Thu, Jun 4, 2020 at 5:30 AM Sean Gleann >>> wrote: >>>> >>>>> Thanks, Gadi. >>>>> Yes, there are GLZ messages associated with these AZDs, but all they >> do >>>> is >>>>> identify the stored failure data. >>>>> >>>>> It's all somewhat moot now. I tried to /P the container, and got told >>> the >>>>> task was non-cancellable. >>>>> Eventually I resorted to a FORCE ARM to get rid of it. >>>>> Restarted the task and now it's running perfectly! No errors or >>> warnings, >>>>> and I'm logged in, ready to start working with my first container. >>>>> >>>>> Sean >>>>> >>>>> On Thu, 4 Jun 2020 at 11:12, Gadi Ben-Avi wrote: >>>>> >>>>>> I found this: >>>>>> >>>>>> >>>>> >>>> >>> >> https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.izso100/izso100_diagnosisservice.htm >>>>>> >>>>>> It looks like the real information is in GLZ messages. >>>>>> >>>>>> I don't have z/OS v2.4 running, so I can't really check. >>>>>> >>>>>> Gadi >>>>>> >>>>>> -Original Message- >>>>>> From: IBM Mainframe Discussion List On >>>> Behalf >>>>>> Of Sean Gleann >>>>>> Sent: Thursday, June 4, 2020 12:53 PM >>>>>> To: IBM-MAIN@LISTSERV.UA.EDU >>>>>> Subject: AZD messages? >>>>>> >>>>>> Can anyone point me at documentation for AZD... messages coming out >>> of >>>> a >>>>>> zcx container, please? >>>>>> >>>>>> I'm getting: >>>>>> AZDN0004E Failure configuring IPv4 address and AZDP0001E >>>> Unexpected >>>>>> error 5 configuring data disks >>>>>> >>>>>> but various attempts at searching for these produce 'nothing found' >>>>>> responses. >>>>>> >>>>>> Regards >>>>>> Sean >>>>>> >>>>>> >>> -- >>>>>> For IBM-MAIN subscribe / signoff / archive access instructions, >> send >>>>> email >>>>>> to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >>>>>> >>>>>> Email secured by Check Point >>>>>> >>>>>> >>> -- >>>>>> For IBM-MAIN subscribe / signoff / archive access instructions, >>>>>> send email to lists...@listserv.ua.edu with the message: INFO >>> IBM-MAIN >>>>>> >>>>> >>>>> >> -- >>>>> For IBM-MAIN subscribe / signoff / archive access instructions, >>>>> send email to lists...@listserv.ua.edu with the message: INFO >> IBM-MAIN >>>>> >>>> -- >>>> Michael Babcock >>>> OneMain Financial >>>> z/OS Systems Programmer, Lead >>>> >>>> -- >>>> For IBM-MAIN subscribe / signoff / archive access instructions, >>>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >>>> >>> >>> -- >>> For IBM-MAIN subscribe / signoff / archive access instructions, >>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >>> >> -- >> Michael Babcock >> OneMain Financial >> z/OS Systems Programmer, Lead >> >> -- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN >> > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: AZD messages?
th these AZDs, but all they > do > > > is > > > > identify the stored failure data. > > > > > > > > It's all somewhat moot now. I tried to /P the container, and got told > > the > > > > task was non-cancellable. > > > > Eventually I resorted to a FORCE ARM to get rid of it. > > > > Restarted the task and now it's running perfectly! No errors or > > warnings, > > > > and I'm logged in, ready to start working with my first container. > > > > > > > > Sean > > > > > > > > On Thu, 4 Jun 2020 at 11:12, Gadi Ben-Avi wrote: > > > > > > > > > I found this: > > > > > > > > > > > > > > > > > > > > https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.izso100/izso100_diagnosisservice.htm > > > > > > > > > > It looks like the real information is in GLZ messages. > > > > > > > > > > I don't have z/OS v2.4 running, so I can't really check. > > > > > > > > > > Gadi > > > > > > > > > > -Original Message- > > > > > From: IBM Mainframe Discussion List On > > > Behalf > > > > > Of Sean Gleann > > > > > Sent: Thursday, June 4, 2020 12:53 PM > > > > > To: IBM-MAIN@LISTSERV.UA.EDU > > > > > Subject: AZD messages? > > > > > > > > > > Can anyone point me at documentation for AZD... messages coming out > > of > > > a > > > > > zcx container, please? > > > > > > > > > > I'm getting: > > > > > AZDN0004E Failure configuring IPv4 address and AZDP0001E > > > Unexpected > > > > > error 5 configuring data disks > > > > > > > > > > but various attempts at searching for these produce 'nothing found' > > > > > responses. > > > > > > > > > > Regards > > > > > Sean > > > > > > > > > > > > -- > > > > > For IBM-MAIN subscribe / signoff / archive access instructions, > send > > > > email > > > > > to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > > > > > > > Email secured by Check Point > > > > > > > > > > > > -- > > > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > > > > send email to lists...@listserv.ua.edu with the message: INFO > > IBM-MAIN > > > > > > > > > > > > > > -- > > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > > > send email to lists...@listserv.ua.edu with the message: INFO > IBM-MAIN > > > > > > > -- > > > Michael Babcock > > > OneMain Financial > > > z/OS Systems Programmer, Lead > > > > > > -- > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > -- > Michael Babcock > OneMain Financial > z/OS Systems Programmer, Lead > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: AZD messages?
Oh and beware, just because the Verify Feature Bits job (and a couple of others) gets a zero condition code doesn’t mean it executed successfully. You have to check STDERR and STDOUT tabs. Mine always gets a syntax error. On Thu, Jun 4, 2020 at 10:05 AM Sean Gleann wrote: > It's been really quite a troublesome effort for me, Michael, but I guess > it's true to say that most of the problems are down to my rudimentary > knowledge of TCPIP and networking in general. > For various reasons, I have to use a tunnelled connection through to the > z/OS guest, and that makes things a bit more interesting. > The 'Getting Started' redbook (SG24-8457-00) has been my sole point of > reference all the way through, and yeah, it's OK - up to point. it doesn't > cover the tunnelling complication, naturally, and there are some very poor > typos to take into account. > As for the Workload Provisioning process in z/OSMF - after you've specified > a bunch of parameters, it's just a JCL generator/job submitter/checker with > a couple of z/OSMF-specific bits thrown in. > During the initial parameter specification phase I had considerable > difficulty at the point of specifying the RSA key, but eventually got it > right. > Step 3.2 in the process - where some sort of version information is looked > for - has always failed for me. I've never been able to make it work as > expected and have had to force it to a 'complete' state by clicking the > 'Finish' button. > > I tried to adapt the process detailed in the redbook to suit our security > set-up, but the result never worked. In the end, I followed the procedure > to the letter, and created the ZCXxxx users and groups in RACF as > specified. > Result - I've finally got a working container that I can log in to. The > next step according to the redbook is to download an image from > hub.docker.com, but when I try the specified command - 'docker pull nginx' > - the container tries to go to registry-1.docker/.io/v2 - which isn't > specified anywhere in the parameter files created by z/OSMF - and it times > out. > I've added suitable mods to \etc\hosts, \etc\ipnodes and to TCPIP.HOSTS, > messed around with DNS specifications and I've commented out the IPSEC > statements in the TCPIP PROFILE parameters (thank gawd for sandbox > systems!). Nothing along those lines has altered the situation. > Now, I'm waiting for our company networking guys to suggest other things to > try. > > Good luck with your efforts, Michael. > I hope you have a smoother ride than I have had so far. > > Sean > > On Thu, 4 Jun 2020 at 15:32, Michael Babcock > wrote: > > > Sean, > > > > I’m just going through the provisioning process now. Any gotchas that > you > > care to share? > > > > On Thu, Jun 4, 2020 at 5:30 AM Sean Gleann > wrote: > > > > > Thanks, Gadi. > > > Yes, there are GLZ messages associated with these AZDs, but all they do > > is > > > identify the stored failure data. > > > > > > It's all somewhat moot now. I tried to /P the container, and got told > the > > > task was non-cancellable. > > > Eventually I resorted to a FORCE ARM to get rid of it. > > > Restarted the task and now it's running perfectly! No errors or > warnings, > > > and I'm logged in, ready to start working with my first container. > > > > > > Sean > > > > > > On Thu, 4 Jun 2020 at 11:12, Gadi Ben-Avi wrote: > > > > > > > I found this: > > > > > > > > > > > > > > https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.izso100/izso100_diagnosisservice.htm > > > > > > > > It looks like the real information is in GLZ messages. > > > > > > > > I don't have z/OS v2.4 running, so I can't really check. > > > > > > > > Gadi > > > > > > > > -Original Message- > > > > From: IBM Mainframe Discussion List On > > Behalf > > > > Of Sean Gleann > > > > Sent: Thursday, June 4, 2020 12:53 PM > > > > To: IBM-MAIN@LISTSERV.UA.EDU > > > > Subject: AZD messages? > > > > > > > > Can anyone point me at documentation for AZD... messages coming out > of > > a > > > > zcx container, please? > > > > > > > > I'm getting: > > > > AZDN0004E Failure configuring IPv4 address and AZDP0001E > > Unexpected > > > > error 5 configuring data disks > > > > > > > > but various attempts at searching for these produce 'nothing found' > > > > responses. > > > > > &g
Re: AZD messages?
3.2, Retrieve workflow version always works for me. 3.5, verify feature bits, always fails with a syntax error. The script being built is too long and gets truncated. I ended up creating my own script and running it. On Thu, Jun 4, 2020 at 10:05 AM Sean Gleann wrote: > It's been really quite a troublesome effort for me, Michael, but I guess > it's true to say that most of the problems are down to my rudimentary > knowledge of TCPIP and networking in general. > For various reasons, I have to use a tunnelled connection through to the > z/OS guest, and that makes things a bit more interesting. > The 'Getting Started' redbook (SG24-8457-00) has been my sole point of > reference all the way through, and yeah, it's OK - up to point. it doesn't > cover the tunnelling complication, naturally, and there are some very poor > typos to take into account. > As for the Workload Provisioning process in z/OSMF - after you've specified > a bunch of parameters, it's just a JCL generator/job submitter/checker with > a couple of z/OSMF-specific bits thrown in. > During the initial parameter specification phase I had considerable > difficulty at the point of specifying the RSA key, but eventually got it > right. > Step 3.2 in the process - where some sort of version information is looked > for - has always failed for me. I've never been able to make it work as > expected and have had to force it to a 'complete' state by clicking the > 'Finish' button. > > I tried to adapt the process detailed in the redbook to suit our security > set-up, but the result never worked. In the end, I followed the procedure > to the letter, and created the ZCXxxx users and groups in RACF as > specified. > Result - I've finally got a working container that I can log in to. The > next step according to the redbook is to download an image from > hub.docker.com, but when I try the specified command - 'docker pull nginx' > - the container tries to go to registry-1.docker/.io/v2 - which isn't > specified anywhere in the parameter files created by z/OSMF - and it times > out. > I've added suitable mods to \etc\hosts, \etc\ipnodes and to TCPIP.HOSTS, > messed around with DNS specifications and I've commented out the IPSEC > statements in the TCPIP PROFILE parameters (thank gawd for sandbox > systems!). Nothing along those lines has altered the situation. > Now, I'm waiting for our company networking guys to suggest other things to > try. > > Good luck with your efforts, Michael. > I hope you have a smoother ride than I have had so far. > > Sean > > On Thu, 4 Jun 2020 at 15:32, Michael Babcock > wrote: > > > Sean, > > > > I’m just going through the provisioning process now. Any gotchas that > you > > care to share? > > > > On Thu, Jun 4, 2020 at 5:30 AM Sean Gleann > wrote: > > > > > Thanks, Gadi. > > > Yes, there are GLZ messages associated with these AZDs, but all they do > > is > > > identify the stored failure data. > > > > > > It's all somewhat moot now. I tried to /P the container, and got told > the > > > task was non-cancellable. > > > Eventually I resorted to a FORCE ARM to get rid of it. > > > Restarted the task and now it's running perfectly! No errors or > warnings, > > > and I'm logged in, ready to start working with my first container. > > > > > > Sean > > > > > > On Thu, 4 Jun 2020 at 11:12, Gadi Ben-Avi wrote: > > > > > > > I found this: > > > > > > > > > > > > > > https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.izso100/izso100_diagnosisservice.htm > > > > > > > > It looks like the real information is in GLZ messages. > > > > > > > > I don't have z/OS v2.4 running, so I can't really check. > > > > > > > > Gadi > > > > > > > > -Original Message- > > > > From: IBM Mainframe Discussion List On > > Behalf > > > > Of Sean Gleann > > > > Sent: Thursday, June 4, 2020 12:53 PM > > > > To: IBM-MAIN@LISTSERV.UA.EDU > > > > Subject: AZD messages? > > > > > > > > Can anyone point me at documentation for AZD... messages coming out > of > > a > > > > zcx container, please? > > > > > > > > I'm getting: > > > > AZDN0004E Failure configuring IPv4 address and AZDP0001E > > Unexpected > > > > error 5 configuring data disks > > > > > > > > but various attempts at searching for these produce 'nothing found' > > > > responses. > > > > > &g
Re: AZD messages?
It's been really quite a troublesome effort for me, Michael, but I guess it's true to say that most of the problems are down to my rudimentary knowledge of TCPIP and networking in general. For various reasons, I have to use a tunnelled connection through to the z/OS guest, and that makes things a bit more interesting. The 'Getting Started' redbook (SG24-8457-00) has been my sole point of reference all the way through, and yeah, it's OK - up to point. it doesn't cover the tunnelling complication, naturally, and there are some very poor typos to take into account. As for the Workload Provisioning process in z/OSMF - after you've specified a bunch of parameters, it's just a JCL generator/job submitter/checker with a couple of z/OSMF-specific bits thrown in. During the initial parameter specification phase I had considerable difficulty at the point of specifying the RSA key, but eventually got it right. Step 3.2 in the process - where some sort of version information is looked for - has always failed for me. I've never been able to make it work as expected and have had to force it to a 'complete' state by clicking the 'Finish' button. I tried to adapt the process detailed in the redbook to suit our security set-up, but the result never worked. In the end, I followed the procedure to the letter, and created the ZCXxxx users and groups in RACF as specified. Result - I've finally got a working container that I can log in to. The next step according to the redbook is to download an image from hub.docker.com, but when I try the specified command - 'docker pull nginx' - the container tries to go to registry-1.docker/.io/v2 - which isn't specified anywhere in the parameter files created by z/OSMF - and it times out. I've added suitable mods to \etc\hosts, \etc\ipnodes and to TCPIP.HOSTS, messed around with DNS specifications and I've commented out the IPSEC statements in the TCPIP PROFILE parameters (thank gawd for sandbox systems!). Nothing along those lines has altered the situation. Now, I'm waiting for our company networking guys to suggest other things to try. Good luck with your efforts, Michael. I hope you have a smoother ride than I have had so far. Sean On Thu, 4 Jun 2020 at 15:32, Michael Babcock wrote: > Sean, > > I’m just going through the provisioning process now. Any gotchas that you > care to share? > > On Thu, Jun 4, 2020 at 5:30 AM Sean Gleann wrote: > > > Thanks, Gadi. > > Yes, there are GLZ messages associated with these AZDs, but all they do > is > > identify the stored failure data. > > > > It's all somewhat moot now. I tried to /P the container, and got told the > > task was non-cancellable. > > Eventually I resorted to a FORCE ARM to get rid of it. > > Restarted the task and now it's running perfectly! No errors or warnings, > > and I'm logged in, ready to start working with my first container. > > > > Sean > > > > On Thu, 4 Jun 2020 at 11:12, Gadi Ben-Avi wrote: > > > > > I found this: > > > > > > > > > https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.izso100/izso100_diagnosisservice.htm > > > > > > It looks like the real information is in GLZ messages. > > > > > > I don't have z/OS v2.4 running, so I can't really check. > > > > > > Gadi > > > > > > -Original Message- > > > From: IBM Mainframe Discussion List On > Behalf > > > Of Sean Gleann > > > Sent: Thursday, June 4, 2020 12:53 PM > > > To: IBM-MAIN@LISTSERV.UA.EDU > > > Subject: AZD messages? > > > > > > Can anyone point me at documentation for AZD... messages coming out of > a > > > zcx container, please? > > > > > > I'm getting: > > > AZDN0004E Failure configuring IPv4 address and AZDP0001E > Unexpected > > > error 5 configuring data disks > > > > > > but various attempts at searching for these produce 'nothing found' > > > responses. > > > > > > Regards > > > Sean > > > > > > -- > > > For IBM-MAIN subscribe / signoff / archive access instructions, send > > email > > > to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > > > Email secured by Check Point > > > > > > -- > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > > > > -- > > For IBM-MAIN subscribe / signoff / arc
Re: AZD messages?
Sean, I’m just going through the provisioning process now. Any gotchas that you care to share? On Thu, Jun 4, 2020 at 5:30 AM Sean Gleann wrote: > Thanks, Gadi. > Yes, there are GLZ messages associated with these AZDs, but all they do is > identify the stored failure data. > > It's all somewhat moot now. I tried to /P the container, and got told the > task was non-cancellable. > Eventually I resorted to a FORCE ARM to get rid of it. > Restarted the task and now it's running perfectly! No errors or warnings, > and I'm logged in, ready to start working with my first container. > > Sean > > On Thu, 4 Jun 2020 at 11:12, Gadi Ben-Avi wrote: > > > I found this: > > > > > https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.izso100/izso100_diagnosisservice.htm > > > > It looks like the real information is in GLZ messages. > > > > I don't have z/OS v2.4 running, so I can't really check. > > > > Gadi > > > > -Original Message- > > From: IBM Mainframe Discussion List On Behalf > > Of Sean Gleann > > Sent: Thursday, June 4, 2020 12:53 PM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: AZD messages? > > > > Can anyone point me at documentation for AZD... messages coming out of a > > zcx container, please? > > > > I'm getting: > > AZDN0004E Failure configuring IPv4 address and AZDP0001E Unexpected > > error 5 configuring data disks > > > > but various attempts at searching for these produce 'nothing found' > > responses. > > > > Regards > > Sean > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, send > email > > to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > Email secured by Check Point > > > > -- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Michael Babcock OneMain Financial z/OS Systems Programmer, Lead -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: AZD messages?
Thanks, Gadi. Yes, there are GLZ messages associated with these AZDs, but all they do is identify the stored failure data. It's all somewhat moot now. I tried to /P the container, and got told the task was non-cancellable. Eventually I resorted to a FORCE ARM to get rid of it. Restarted the task and now it's running perfectly! No errors or warnings, and I'm logged in, ready to start working with my first container. Sean On Thu, 4 Jun 2020 at 11:12, Gadi Ben-Avi wrote: > I found this: > > https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.izso100/izso100_diagnosisservice.htm > > It looks like the real information is in GLZ messages. > > I don't have z/OS v2.4 running, so I can't really check. > > Gadi > > -Original Message- > From: IBM Mainframe Discussion List On Behalf > Of Sean Gleann > Sent: Thursday, June 4, 2020 12:53 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: AZD messages? > > Can anyone point me at documentation for AZD... messages coming out of a > zcx container, please? > > I'm getting: > AZDN0004E Failure configuring IPv4 address and AZDP0001E Unexpected > error 5 configuring data disks > > but various attempts at searching for these produce 'nothing found' > responses. > > Regards > Sean > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, send email > to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > Email secured by Check Point > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: AZD messages?
I found this: https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.izso100/izso100_diagnosisservice.htm It looks like the real information is in GLZ messages. I don't have z/OS v2.4 running, so I can't really check. Gadi -Original Message- From: IBM Mainframe Discussion List On Behalf Of Sean Gleann Sent: Thursday, June 4, 2020 12:53 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: AZD messages? Can anyone point me at documentation for AZD... messages coming out of a zcx container, please? I'm getting: AZDN0004E Failure configuring IPv4 address and AZDP0001E Unexpected error 5 configuring data disks but various attempts at searching for these produce 'nothing found' responses. Regards Sean -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Email secured by Check Point -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
AZD messages?
Can anyone point me at documentation for AZD... messages coming out of a zcx container, please? I'm getting: AZDN0004E Failure configuring IPv4 address and AZDP0001E Unexpected error 5 configuring data disks but various attempts at searching for these produce 'nothing found' responses. Regards Sean -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
