Re: FICON "Invalid attachment failure"
Radoslaw, What are we talking about here? Cisco or Brocade? Which model? What was the 'exact' message logged in the switch itself? Regards, Alan Watthey -Original Message- From: R.S. Sent: 22 August 2018 1:17 pm Subject: FICON "Invalid attachment failure" Two FICON channels were connected to a switch. Both signal an error "Invalid attachment failure" (this is visible on SE) I checked port#, zoning, HCD/IODF and have no idea what to check futher. z13 FICON Express16S, DCX8510-4 with 8Gbps SFP. Any clue? -- Radoslaw Skorupka Lodz, Poland == Jeśli nie jesteś adresatem tej wiadomości: - powiadom nas o tym w mailu zwrotnym (dziękujemy!), - usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś na dysku). Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać tylko adresat.Przypominamy, że każdy, kto rozpowszechnia (kopiuje, rozprowadza) tę wiadomość lub podejmuje podobne działania, narusza prawo i może podlegać karze. mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 025237, NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na 01.01.2018 r. wynosi 169.248.488 złotych. If you are not the addressee of this message: - let us know by replying to this e-mail (thank you!), - delete this message permanently (including all the copies which you have printed out or saved). This message may contain legally protected information, which may be used exclusively by the addressee.Please be reminded that anyone who disseminates (copies, distributes) this message or takes any similar action, violates the law and may be penalised. mBank S.A. with its registered office in Warsaw, ul. Senatorska 18, 00-950 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. District Court for the Capital City of Warsaw, 12th Commercial Division of the National Court Register, KRS 025237, NIP: 526-021-50-88. Fully paid-up share capital amounting to PLN 169,248,488 as at 1 January 2018. -- 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: Anyone here exprerienced in JSON parser (assembler)
On 23/08/2018 7:44 AM, Steve Smith wrote: Recursion in assembler is hardly difficult. Knowing how to implement a stack is fundamental. Smart programmers not only do, but haven't even thought about it other than when architecture improvements require an upgrade. Why do t you Demi started to us how easy it is? Apologies for the gibberish! Mangled by my iPad spell checker :) I meant why don't you "demonstrate" how easy recursion is in assembler using a stack? It may be trivial to use a fixed sized stack and macros but it's not easy to do a full stack frame implementation that handles overflow like LE. We've all seen how Metal/C uses the NAB pointer for it's stack frames and that's not without it's issues if you don't keep track of how much storage you need. sas p.s. Aha! Spellchecker wants to replace Crayford with Crawford. I will have it whipped :-) On 8/22/2018 18:39, David Crayford wrote: On 23/08/2018 12:46 AM, Kirk Wolf wrote: I've used the IBM JSON parser, from C. I don't see why it would be ill suited for assembler more than anything else :-) I'm doing a lot of JSON work right now and one task was to create a JSON to YAML convertor for swagger documents. The elegant solution was to use recursion which is difficult to do in assembler. It's difficult to do in COBOL too. -- 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: Anyone here exprerienced in JSON parser (assembler)
Why do t you Demi started to us how easy it is? > On 23 Aug 2018, at 12:46 am, Kirk Wolf wrote: > > I've used the IBM JSON parser, from C. > I don't see why it would be ill suited for assembler more than anything > else :-) > >> On Wed, Aug 22, 2018 at 10:51 AM Charles Mills wrote: >> >> *Personally* I agree, but different languages for different folks. Some >> people are very comfortable in assembler, especially with the structured >> macros. I think I can state with some confidence that if @EdJaffe need to >> parse some JSON documents he would do it from assembler. >> >> COBOL does not seem like a great choice either to me personally, but some >> folks, and especially some shops, are most comfortable with COBOL. >> >> Charles >> >> -Original Message- >> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On >> Behalf Of David Crayford >> >> IMO, assembler isn't the right language to be parsing complex JSON >> documents. I couldn't think of a worse >> language for the job. >> >> -- >> 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: Anyone here exprerienced in JSON parser (assembler)
Recursion in assembler is hardly difficult. Knowing how to implement a stack is fundamental. Smart programmers not only do, but haven't even thought about it other than when architecture improvements require an upgrade. sas p.s. Aha! Spellchecker wants to replace Crayford with Crawford. I will have it whipped :-) On 8/22/2018 18:39, David Crayford wrote: On 23/08/2018 12:46 AM, Kirk Wolf wrote: I've used the IBM JSON parser, from C. I don't see why it would be ill suited for assembler more than anything else :-) I'm doing a lot of JSON work right now and one task was to create a JSON to YAML convertor for swagger documents. The elegant solution was to use recursion which is difficult to do in assembler. It's difficult to do in COBOL too. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Anyone here exprerienced in JSON parser (assembler)
On 23/08/2018 12:46 AM, Kirk Wolf wrote: I've used the IBM JSON parser, from C. I don't see why it would be ill suited for assembler more than anything else :-) I'm doing a lot of JSON work right now and one task was to create a JSON to YAML convertor for swagger documents. The elegant solution was to use recursion which is difficult to do in assembler. It's difficult to do in COBOL too. I would be interested to know why you used the IBM JSON parser? One only has to browse the C sample in SYS1.SAMPLIB to conclude it's a inelegant beast with a bloated API. I can only assume that you were working on a project that precluded open source software? I've used several open source C/C++ JSON libraries on z/OS. They're easy to port (just tweaked to handle UTF8 escape sequences if you want to process EBCDIC). I've used YAJL [1] from C but much prefer C++ libraries with map like interfaces and STL compatible iterators. JsonCpp [2] is quite good but I prefer picojson [3] which also has a streaming API. [1] https://github.com/lloyd/yajl [2] http://open-source-parsers.github.io/jsoncpp-docs/doxygen/index.html [3] https://github.com/kazuho/picojson On Wed, Aug 22, 2018 at 10:51 AM Charles Mills wrote: *Personally* I agree, but different languages for different folks. Some people are very comfortable in assembler, especially with the structured macros. I think I can state with some confidence that if @EdJaffe need to parse some JSON documents he would do it from assembler. COBOL does not seem like a great choice either to me personally, but some folks, and especially some shops, are most comfortable with COBOL. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of David Crayford IMO, assembler isn't the right language to be parsing complex JSON documents. I couldn't think of a worse language for the job. -- 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
Encryption keys and EM waves
While the keys that are processed in the Crypto Express cards should be safe.. I am less sure about anything else. https://www.bleepingcomputer.com/news/security/new-attack-recovers-rsa-encryption-keys-from-em-waves-within-seconds/ Rob Schramm -- Rob Schramm -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FICON "Invalid attachment failure"
Have you tried to clean the fibre? >W dniu 2018-08-22 o 13:45, Roger Lowe pisze: >> On Wed, 22 Aug 2018 12:16:53 +0200, R.S. >> wrote: >> >>> Two FICON channels were connected to a switch. >>> Both signal an error "Invalid attachment failure" (this is visible on SE) >>> I checked port#, zoning, HCD/IODF and have no idea what to check futher. >>> z13 FICON Express16S, DCX8510-4 with 8Gbps SFP. >>> >>> >>> Any clue? >> Try invoking the 'Channel Problem Determination' task on the HMC. There are >> various options associated with that task and hopefully that might give you >> a clue where the issue(s) may lie. > >I did. All the options. >I see "Not valid" as the other node (that means switch port) with no >details, except port speed. >The switch show the port as not connected, although Statistics show some >frames were exchanged. >The only thing is connection rate. It is set to real value. Indeed, it >is FICON Ex16 to 8Gbps SFP, but I also enforced 4Gbps on switch side >and "Analyze Channel Information" shows actual speed. So, the speed >negotiation was done succesfully. Something bad happened after that. > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: TESTAUTH BRANCH=XM ?
Though there has been the occasional thing that has lacked only the doc, or is documented only in the macro, so worth asking. > If you need this function, then please submit an RFE. It's a would-be-nice. I can program around it. OTOH if it's been there for 15 years, is it really likely to go away? It's not going to go away. We use it. It was written because we needed it. Having an RFE is primarily to help the powers that be justify the work of documenting it. Peter Relson z/OS Core Technology Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
September Hillgang Meeting
The next Hillgang meeting will take place on 13 Sep at the CA offices in Herndon. Detailed agenda to follow but in brief we will have: * Ever Onward with z/VM 7.1 – Bill Bitner, IBM * z/VM Dynamic Memory Management – Walter Church, IBM * What’s Z Story at Marriott – Kurt Ackers, Marriott * Open Mainframe Project Mainframe Study Update – Len Santalucia, Vicom * Managing and Orchestrating Docker Containers with OpenShift – Neale Ferguson, SNA Register at https://doodle.com/poll/hkyb5sq8w32garh8 Neale -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Anyone here exprerienced in JSON parser (assembler)
I've used the IBM JSON parser, from C. I don't see why it would be ill suited for assembler more than anything else :-) On Wed, Aug 22, 2018 at 10:51 AM Charles Mills wrote: > *Personally* I agree, but different languages for different folks. Some > people are very comfortable in assembler, especially with the structured > macros. I think I can state with some confidence that if @EdJaffe need to > parse some JSON documents he would do it from assembler. > > COBOL does not seem like a great choice either to me personally, but some > folks, and especially some shops, are most comfortable with COBOL. > > Charles > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of David Crayford > > IMO, assembler isn't the right language to be parsing complex JSON > documents. I couldn't think of a worse > language for the job. > > -- > 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: Anyone here exprerienced in JSON parser (assembler)
*Personally* I agree, but different languages for different folks. Some people are very comfortable in assembler, especially with the structured macros. I think I can state with some confidence that if @EdJaffe need to parse some JSON documents he would do it from assembler. COBOL does not seem like a great choice either to me personally, but some folks, and especially some shops, are most comfortable with COBOL. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of David Crayford IMO, assembler isn't the right language to be parsing complex JSON documents. I couldn't think of a worse language for the job. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Anyone here exprerienced in JSON parser (assembler)
AWK? BASIC? RPG? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of David Crayford Sent: Wednesday, August 22, 2018 2:47 AM To: IBM-MAIN@listserv.ua.edu Subject: Re: Anyone here exprerienced in JSON parser (assembler) On 22/08/2018 12:02 PM, ITschak Mugzach wrote: > I am reading IBM manuals for about 40 years, and it is hard to understand > the flow of the interface calls from the manual. I first wrote a rexx > program just to understand the flow. It also helped me to understand why > assembler calls are not executing well. I am not sure this is a proper tool > for parsing a complex, array structured JSON. IMO, assembler isn't the right language to be parsing complex JSON documents. I couldn't think of a worse language for the job. -- 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: FICON "Invalid attachment failure"
W dniu 2018-08-22 o 13:45, Roger Lowe pisze: On Wed, 22 Aug 2018 12:16:53 +0200, R.S. wrote: Two FICON channels were connected to a switch. Both signal an error "Invalid attachment failure" (this is visible on SE) I checked port#, zoning, HCD/IODF and have no idea what to check futher. z13 FICON Express16S, DCX8510-4 with 8Gbps SFP. Any clue? Try invoking the 'Channel Problem Determination' task on the HMC. There are various options associated with that task and hopefully that might give you a clue where the issue(s) may lie. I did. All the options. I see "Not valid" as the other node (that means switch port) with no details, except port speed. The switch show the port as not connected, although Statistics show some frames were exchanged. The only thing is connection rate. It is set to real value. Indeed, it is FICON Ex16 to 8Gbps SFP, but I also enforced 4Gbps on switch side and "Analyze Channel Information" shows actual speed. So, the speed negotiation was done succesfully. Something bad happened after that. -- Radoslaw Skorupka Lodz, Poland == Jeśli nie jesteś adresatem tej wiadomości: - powiadom nas o tym w mailu zwrotnym (dziękujemy!), - usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś na dysku). Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać tylko adresat.Przypominamy, że każdy, kto rozpowszechnia (kopiuje, rozprowadza) tę wiadomość lub podejmuje podobne działania, narusza prawo i może podlegać karze. mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 025237, NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na 01.01.2018 r. wynosi 169.248.488 złotych. If you are not the addressee of this message: - let us know by replying to this e-mail (thank you!), - delete this message permanently (including all the copies which you have printed out or saved). This message may contain legally protected information, which may be used exclusively by the addressee.Please be reminded that anyone who disseminates (copies, distributes) this message or takes any similar action, violates the law and may be penalised. mBank S.A. with its registered office in Warsaw, ul. Senatorska 18, 00-950 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. District Court for the Capital City of Warsaw, 12th Commercial Division of the National Court Register, KRS 025237, NIP: 526-021-50-88. Fully paid-up share capital amounting to PLN 169,248,488 as at 1 January 2018. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FICON "Invalid attachment failure"
With you being on a z13 and if you are on z/OS 2.2 you could try the D M=DEV(,(xx)),LINKINFO=LAST command to see what things look like. It might show you information that might help. Thanks.. Paul Feller AGT Mainframe Technical Support -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of R.S. Sent: Wednesday, August 22, 2018 5:17 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: FICON "Invalid attachment failure" Two FICON channels were connected to a switch. Both signal an error "Invalid attachment failure" (this is visible on SE) I checked port#, zoning, HCD/IODF and have no idea what to check futher. z13 FICON Express16S, DCX8510-4 with 8Gbps SFP. Any clue? -- Radoslaw Skorupka Lodz, Poland == Jeśli nie jesteś adresatem tej wiadomości: - powiadom nas o tym w mailu zwrotnym (dziękujemy!), - usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś na dysku). Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać tylko adresat.Przypominamy, że każdy, kto rozpowszechnia (kopiuje, rozprowadza) tę wiadomość lub podejmuje podobne działania, narusza prawo i może podlegać karze. mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 025237, NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na 01.01.2018 r. wynosi 169.248.488 złotych. If you are not the addressee of this message: - let us know by replying to this e-mail (thank you!), - delete this message permanently (including all the copies which you have printed out or saved). This message may contain legally protected information, which may be used exclusively by the addressee.Please be reminded that anyone who disseminates (copies, distributes) this message or takes any similar action, violates the law and may be penalised. mBank S.A. with its registered office in Warsaw, ul. Senatorska 18, 00-950 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. District Court for the Capital City of Warsaw, 12th Commercial Division of the National Court Register, KRS 025237, NIP: 526-021-50-88. Fully paid-up share capital amounting to PLN 169,248,488 as at 1 January 2018. -- 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: FICON "Invalid attachment failure"
Also noted that you have FICON Express16s with 8Gbps SFP - have you checked that the port you are using on the switch is at 8Gbps? >On Wed, 22 Aug 2018 12:16:53 +0200, R.S. >wrote: > >>Two FICON channels were connected to a switch. >>Both signal an error "Invalid attachment failure" (this is visible on SE) >>I checked port#, zoning, HCD/IODF and have no idea what to check futher. >>z13 FICON Express16S, DCX8510-4 with 8Gbps SFP. >> >> >>Any clue? >Try invoking the 'Channel Problem Determination' task on the HMC. There are >various options associated with that task and hopefully that might give you a >clue where the issue(s) may lie. > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FICON "Invalid attachment failure"
On Wed, 22 Aug 2018 12:16:53 +0200, R.S. wrote: >Two FICON channels were connected to a switch. >Both signal an error "Invalid attachment failure" (this is visible on SE) >I checked port#, zoning, HCD/IODF and have no idea what to check futher. >z13 FICON Express16S, DCX8510-4 with 8Gbps SFP. > > >Any clue? Try invoking the 'Channel Problem Determination' task on the HMC. There are various options associated with that task and hopefully that might give you a clue where the issue(s) may lie. Hope that helps. Roger -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FICON "Invalid attachment failure"
Maybe a port not assigned? Check the switch's log? On Wed, Aug 22, 2018 at 5:26 AM R.S. wrote: > > W dniu 2018-08-22 o 12:22, Mike Schwab pisze: > > System log. sys1.logrec > "IEE712I CONFIG PROCESSING COMPLETE" > That's all > > -- > Radoslaw Skorupka > Lodz, Poland > > > > > == > > Jeśli nie jesteś adresatem tej wiadomości: > > - powiadom nas o tym w mailu zwrotnym (dziękujemy!), > - usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub > zapisałeś na dysku). > Wiadomość ta może zawierać chronione prawem informacje, które może > wykorzystać tylko adresat.Przypominamy, że każdy, kto rozpowszechnia > (kopiuje, rozprowadza) tę wiadomość lub podejmuje podobne działania, narusza > prawo i może podlegać karze. > > mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 > Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st. > Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 025237, > NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na > 01.01.2018 r. wynosi 169.248.488 złotych. > > If you are not the addressee of this message: > > - let us know by replying to this e-mail (thank you!), > - delete this message permanently (including all the copies which you have > printed out or saved). > This message may contain legally protected information, which may be used > exclusively by the addressee.Please be reminded that anyone who disseminates > (copies, distributes) this message or takes any similar action, violates the > law and may be penalised. > > mBank S.A. with its registered office in Warsaw, ul. Senatorska 18, 00-950 > Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. District Court for the > Capital City of Warsaw, 12th Commercial Division of the National Court > Register, KRS 025237, NIP: 526-021-50-88. Fully paid-up share capital > amounting to PLN 169,248,488 as at 1 January 2018. > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FICON "Invalid attachment failure"
W dniu 2018-08-22 o 12:22, Mike Schwab pisze: System log. sys1.logrec "IEE712I CONFIG PROCESSING COMPLETE" That's all -- Radoslaw Skorupka Lodz, Poland == Jeśli nie jesteś adresatem tej wiadomości: - powiadom nas o tym w mailu zwrotnym (dziękujemy!), - usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś na dysku). Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać tylko adresat.Przypominamy, że każdy, kto rozpowszechnia (kopiuje, rozprowadza) tę wiadomość lub podejmuje podobne działania, narusza prawo i może podlegać karze. mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 025237, NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na 01.01.2018 r. wynosi 169.248.488 złotych. If you are not the addressee of this message: - let us know by replying to this e-mail (thank you!), - delete this message permanently (including all the copies which you have printed out or saved). This message may contain legally protected information, which may be used exclusively by the addressee.Please be reminded that anyone who disseminates (copies, distributes) this message or takes any similar action, violates the law and may be penalised. mBank S.A. with its registered office in Warsaw, ul. Senatorska 18, 00-950 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. District Court for the Capital City of Warsaw, 12th Commercial Division of the National Court Register, KRS 025237, NIP: 526-021-50-88. Fully paid-up share capital amounting to PLN 169,248,488 as at 1 January 2018. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: FICON "Invalid attachment failure"
System log. sys1.logrec On Wed, Aug 22, 2018 at 5:17 AM R.S. wrote: > > Two FICON channels were connected to a switch. > Both signal an error "Invalid attachment failure" (this is visible on SE) > I checked port#, zoning, HCD/IODF and have no idea what to check futher. > z13 FICON Express16S, DCX8510-4 with 8Gbps SFP. > > > Any clue? > > -- > Radoslaw Skorupka > Lodz, Poland > > > > > == > > Jeśli nie jesteś adresatem tej wiadomości: > > - powiadom nas o tym w mailu zwrotnym (dziękujemy!), > - usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub > zapisałeś na dysku). > Wiadomość ta może zawierać chronione prawem informacje, które może > wykorzystać tylko adresat.Przypominamy, że każdy, kto rozpowszechnia > (kopiuje, rozprowadza) tę wiadomość lub podejmuje podobne działania, narusza > prawo i może podlegać karze. > > mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 > Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st. > Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 025237, > NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na > 01.01.2018 r. wynosi 169.248.488 złotych. > > If you are not the addressee of this message: > > - let us know by replying to this e-mail (thank you!), > - delete this message permanently (including all the copies which you have > printed out or saved). > This message may contain legally protected information, which may be used > exclusively by the addressee.Please be reminded that anyone who disseminates > (copies, distributes) this message or takes any similar action, violates the > law and may be penalised. > > mBank S.A. with its registered office in Warsaw, ul. Senatorska 18, 00-950 > Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. District Court for the > Capital City of Warsaw, 12th Commercial Division of the National Court > Register, KRS 025237, NIP: 526-021-50-88. Fully paid-up share capital > amounting to PLN 169,248,488 as at 1 January 2018. > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
FICON "Invalid attachment failure"
Two FICON channels were connected to a switch. Both signal an error "Invalid attachment failure" (this is visible on SE) I checked port#, zoning, HCD/IODF and have no idea what to check futher. z13 FICON Express16S, DCX8510-4 with 8Gbps SFP. Any clue? -- Radoslaw Skorupka Lodz, Poland == Jeśli nie jesteś adresatem tej wiadomości: - powiadom nas o tym w mailu zwrotnym (dziękujemy!), - usuń trwale tę wiadomość (i wszystkie kopie, które wydrukowałeś lub zapisałeś na dysku). Wiadomość ta może zawierać chronione prawem informacje, które może wykorzystać tylko adresat.Przypominamy, że każdy, kto rozpowszechnia (kopiuje, rozprowadza) tę wiadomość lub podejmuje podobne działania, narusza prawo i może podlegać karze. mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru Sądowego, KRS 025237, NIP: 526-021-50-88. Kapitał zakładowy (opłacony w całości) według stanu na 01.01.2018 r. wynosi 169.248.488 złotych. If you are not the addressee of this message: - let us know by replying to this e-mail (thank you!), - delete this message permanently (including all the copies which you have printed out or saved). This message may contain legally protected information, which may be used exclusively by the addressee.Please be reminded that anyone who disseminates (copies, distributes) this message or takes any similar action, violates the law and may be penalised. mBank S.A. with its registered office in Warsaw, ul. Senatorska 18, 00-950 Warszawa,www.mBank.pl, e-mail: kont...@mbank.pl. District Court for the Capital City of Warsaw, 12th Commercial Division of the National Court Register, KRS 025237, NIP: 526-021-50-88. Fully paid-up share capital amounting to PLN 169,248,488 as at 1 January 2018. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Anyone here exprerienced in JSON parser (assembler)
Aha On Wed, Aug 22, 2018 at 10:03 AM David Crayford wrote: > On 22/08/2018 9:42 AM, Doug wrote: > > Galina, > > Yes, it would be worth providing sample code for batch assembler, CICS > assembler, CICS COBOL , CICS REXX , TSO REXX and ‘how to’ direction for > Liberty and eclipse. Sorry if I missed some, feel free to chime in. > > > I think you'll be living in hope if you expect that lot! CICS COBOL will > almost certainly use CICS JSON web services. Liberty and Eclipse are > Java environments so parsing JSON is as simple as using an annotation > based library like Jackson. > As for assembler, if somebody really wants to parse JSON in a 2GL they > should be smart enough to understand the documentation :) > > > > By sample code we mean fully functional examples not a small KC tribute > to a hint and click for KC to direct us to yet another tiny hint. > > Just my 2cents.. > > Most of us are swamped with day to day problems and don’t have the extra > band width to explore as we did in days gone by. > > Best Regards, > > Doug > > > > . > > > > On Aug 21, 2018, at 15:08, Galina Gorelik wrote: > > > > Hi ITschak, > > > > I’m part of the team that develops the z/OS JSON parser. From your > previous post, it appears you have resolved the issue you were experiencing. > > As you pointed out, we do not provider assembler samples, so you have to > connect the dots between the following three things: > > 1. IBM Knowledge Center, z/OS JSON parser: Description of > HWTJ_SEARCHTYPE_GLOBAL that distinguishes between the REXX and non-REXX > parameter content: for the first “name” that exactly matches the > SearchString for REXX or the string pointed to by the SearchStringAddr > parameter for non-REXX. > > 2. IBM Knowledge Center, z/OS JSON parser: Linkage considerations for > assembler language programming that specifies: Register 1 must contain the > address of a parameter list that is a list of consecutive words, each > containing the address of a parameter to be passed. > > 3. HWTJIASM macro: HWTJSRCH input parameters section where the > HWTJSRCHPARMLIST DSECT shows that these are all pointers to the parameters, > in the case of the SearchStringAddr parameter, the DS indicates that this > is a pointer to the address: HWTJSRCHSEARCHSTRINGADDRPTRDS A Address > of SearchStringAddr > > > > Is there additional information that can be added that would have helped > more? Or verbiage that should be altered? > > > > Galina > > > > -- > > 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 > -- ITschak Mugzach *|** IronSphere Platform* *|* *Information Security Contiguous Monitoring for Legacy **| * -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Anyone here exprerienced in JSON parser (assembler)
On 22/08/2018 9:42 AM, Doug wrote: Galina, Yes, it would be worth providing sample code for batch assembler, CICS assembler, CICS COBOL , CICS REXX , TSO REXX and ‘how to’ direction for Liberty and eclipse. Sorry if I missed some, feel free to chime in. I think you'll be living in hope if you expect that lot! CICS COBOL will almost certainly use CICS JSON web services. Liberty and Eclipse are Java environments so parsing JSON is as simple as using an annotation based library like Jackson. As for assembler, if somebody really wants to parse JSON in a 2GL they should be smart enough to understand the documentation :) By sample code we mean fully functional examples not a small KC tribute to a hint and click for KC to direct us to yet another tiny hint. Just my 2cents.. Most of us are swamped with day to day problems and don’t have the extra band width to explore as we did in days gone by. Best Regards, Doug . On Aug 21, 2018, at 15:08, Galina Gorelik wrote: Hi ITschak, I’m part of the team that develops the z/OS JSON parser. From your previous post, it appears you have resolved the issue you were experiencing. As you pointed out, we do not provider assembler samples, so you have to connect the dots between the following three things: 1. IBM Knowledge Center, z/OS JSON parser: Description of HWTJ_SEARCHTYPE_GLOBAL that distinguishes between the REXX and non-REXX parameter content: for the first “name” that exactly matches the SearchString for REXX or the string pointed to by the SearchStringAddr parameter for non-REXX. 2. IBM Knowledge Center, z/OS JSON parser: Linkage considerations for assembler language programming that specifies: Register 1 must contain the address of a parameter list that is a list of consecutive words, each containing the address of a parameter to be passed. 3. HWTJIASM macro: HWTJSRCH input parameters section where the HWTJSRCHPARMLIST DSECT shows that these are all pointers to the parameters, in the case of the SearchStringAddr parameter, the DS indicates that this is a pointer to the address: HWTJSRCHSEARCHSTRINGADDRPTRDS A Address of SearchStringAddr Is there additional information that can be added that would have helped more? Or verbiage that should be altered? Galina -- 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: Anyone here exprerienced in JSON parser (assembler)
On 22/08/2018 12:02 PM, ITschak Mugzach wrote: I am reading IBM manuals for about 40 years, and it is hard to understand the flow of the interface calls from the manual. I first wrote a rexx program just to understand the flow. It also helped me to understand why assembler calls are not executing well. I am not sure this is a proper tool for parsing a complex, array structured JSON. IMO, assembler isn't the right language to be parsing complex JSON documents. I couldn't think of a worse language for the job. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IBM Announcing New DS8882F Enterprise Storage
I believe it comes with it's own HMC function within the 16U space, but it uses the same keyboard/monitor/mouse (KMM) that the Support Elements (SE) of Z use. The z14 ZR1/LR1 has a KVM switch which permits the KMM to be switched between the SE or the DS8882F. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
