VTOC extended
Hi all The size of VTOC is smaller,we want to extend VTOC using the following JCL . // EXEC PGM=ICKDSF //DD1 DD DISP=SHR,UNIT=3390,VOL=SER=xx //SYSPRINT DD SYSOUT=A //SYSIN DD * REFORMAT DDNAME(DD1) VERIFY(xx) EXTVTOC(30) EXTINDEX(15) Run REFORMAT EXTVTOC(n) where 'n' is the total size of the new VTOC in tracks. There must be free space available to allow for contiguous expansion of the VTOC. If there isn'tfree space available following the current location of the VTOC, an error message will be issued. 'n' must be greater than the old VTOC size. Before running REFORMAT EXTVTOC(n),is there any utility or REXX t which could tell whether there is any free space available following the current location of the VTOC? Thanks a lot! Best Regards, Jason Cai -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SUBSYS=?
Mike Kerford-Byrnes wrote: >P.S. 2 - Is there an index of ALL the topic titles for the Xephon Manuals in a >given set held on the CBTTAPE site? So far all I have been able to find is >the once a year accumulation - but I have to look at each month's worth until >I find it. It would be helpful, especially in cases such as this to have a >listing of all of the topics in, say, all of the Xephon MVS Updates held on >the CBTTAPE site. Are you refering to this: http://www.cbttape.org/xephon/ ? Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
SUBSYS=?
Digging around in some old boxes, I found some references to the Subsystem Interface. All are old, and may be difficult to locate. I do not have any of them in my possession, but if they are useful, be my guest. Xephon MVS update Issues 24 and 25 (September/October 1988) explaining MVS SSI. Xephon MVS update (2 consecutive months sometime between 1991 and 1992) "Development of an MVS Subsystem by Walter Wiedermann. LY28-1496 - MVS/ESA Component Diagnosis and Logic - Master Subsystem/Subsystem Interface. GG66-3131 The Subsystem interface in MVS/SP Version 3. SR21- 1469 - A guide to using MVS/XA Interface facilities (Chapter 9). Mainframe Journal - March 1989 page 69 - Subsystem Interface Component of MVS I did say they were old. Mike Kerford-Byrnes. P.S. 1 - Has anyone looked in the Candle Computer reports? P.S. 2 - Is there an index of ALL the topic titles for the Xephon Manuals in a given set held on the CBTTAPE site? So far all I have been able to find is the once a year accumulation - but I have to look at each month's worth until I find it. It would be helpful, especially in cases such as this to have a listing of all of the topics in, say, all of the Xephon MVS Updates held on the CBTTAPE site. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: C/C++ Runtime Library
On Wed, 8 Nov 2017, at 22:48, Paul Gilmartin wrote: > "P-Code" sounds like jargon from UCSD Pascal, which I brushed > against 30+ years ago. There was no pass two; there was an > interpreter for the P-Code. I've always associated P-code with Wirth's Pascal compiler. But it turns out that the term is more general than that, and even for Pascal is relevant to several early compilers. See: https://en.wikipedia.org/wiki/P-code_machine -- Jeremy Nicoll - my opinions are my own. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Are JZOS JVM loader excutables installed in PDSE libraries?
On Wed, 8 Nov 2017 19:22:58 +, Farley, Peter x23353 wrote: >Of course. At the moment I do not know by whom or how it was installed, nor >even when. That it is installed at all is good news for me, but the how and >why are not known. > But they shouldn't take the short cut of assuming that since it's almost done they can simply copy to a PDSE. That works well only until there's a PTF. >That is why I need to engage the systems team, which is a process not under my >control. All I can do is ask via the prescribed management interfaces. >Isn't "the right thing" to install using SMP/E? -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: C/C++ Runtime Library
On Wed, 8 Nov 2017 23:20:41 +0100, Bernd Oppolzer wrote: > >Just to give an example, how small a runtime library can be: > >my New Stanford Pascal compiler has a runtime library, which is also linked >with every >Pascal program (in the same way as Dave describes). The Pascal compiler itself >is >a Pascal program (ca. 15.000 lines at the moment - pass one, generating >P-Code; the >P-Code is later translated to 370 machine code, which is done in pass two, >which has >another 12000 lines). For the following discussion, PASCAL1 (pass one) only >serves as >an example of a (large) Pascal program. > "P-Code" sounds like jargon from UCSD Pascal, which I brushed against 30+ years ago. There was no pass two; there was an interpreter for the P-Code. (In other jargon) The runtime library was a single large load module which was linked with every program. But there was a "smart linker" which filtered that large object and deleted every unreferenced CSECT, making the executable as small as possible. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: C/C++ Runtime Library
Am 08.11.2017 um 18:47 schrieb Thomas David Rivers: Frank Swarbrick wrote: Doesn't that make for fairly large executables? Well - it can - but a trimmed down C library is surprisingly small. Of course - if you're dragging C++ into this, then things get bigger; but again - that's not the library usually, it's the templates, etc.. that your program instantiates... It seems, in practice, to not be an issue at all. - Dave Rivers - Just to give an example, how small a runtime library can be: my New Stanford Pascal compiler has a runtime library, which is also linked with every Pascal program (in the same way as Dave describes). The Pascal compiler itself is a Pascal program (ca. 15.000 lines at the moment - pass one, generating P-Code; the P-Code is later translated to 370 machine code, which is done in pass two, which has another 12000 lines). For the following discussion, PASCAL1 (pass one) only serves as an example of a (large) Pascal program. Pass one has, after compilation, the following size: ENTRY ADDRESS 1E940 TOTAL LENGTH 30AC8 PASCAL1 NOW REPLACED IN DATA SET AUTHORIZATION CODE IS 0. the size of PASCAL1 is 200 k, ca. Excerpts from the Linker listing: CONTROL SECTION ENTRY NAME ORIGIN LENGTH NAME LOCATION NAME LOCATION $PASMAI# 00 E28 $PRV0001 E28 AC $PRV0002 ED8 C8 $PRV0003 FA0 E8 $PRV0004 1088 78 The runtime starts here: $PASENT 1E940 53E0 $PASINT 1EE88 $PASTRC 1F0CC IHNERRM 1FB36 ERRMON 1FB36 IHCERRE 1FB6A $PASSYS 1FB78 $PASCSP2 2005A $PASLIB# 23D20 2C $LIBX002 23D50 BC $LIBX004 23E10 118 that is: the "core" runtime, written in ASSEMBLER, is $PASENT, and its size is 21 k (!). The "library" functions from $PASLIB (written in Pascal) are added for convenience, although only very few of them are really used in the compiler. All those "library" function are located in the area from 23D20 to 30AC8 and need 52 k ca. BTW: I just discovered that I added an unneeded member called PASUTILS, which could be eliminated, so 8 k could by saved :-) $PASUTI# 2E938 4A $UTIL003 2E988 C0 HALT 2EA48 A4 DATETIME 2EAF0 184 DATTIM10 2EC78 1C4 TERMIN 2EE40 290 TERMOUT 2F0D0 290 ASSIGN 2F360 320 ASSIGNME 2F680 1A4 CLRSCRN 2F828 1B8 MOVEPARM 2F9E0 178 TOUPPER 2FB58 104 TOUPPERS 2FC60 10C $UTIL016 2FD70 118 $UTIL017 2FE88 33C DUMPSTOR 301C8 138 INTTOSTR 30300 284 IVALSTR 30588 3F8 READSYMB 30980 144 if you are interested in the compiler, look here: http://bernd-oppolzer.de/job9.htm or here: https://www.facebook.com/StanfordPascal/?ref=aymt_homepage_panel the compiler runs on old CMS and MVS versions, but on modern z/OS, too (limited to AMODE 24, at the moment), and probably on z/VM (not tested yet). You can download the compiler using the links above. Kind regards Bernd -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Are JZOS JVM loader excutables installed in PDSE libraries?
Of course. At the moment I do not know by whom or how it was installed, nor even when. That it is installed at all is good news for me, but the how and why are not known. That is why I need to engage the systems team, which is a process not under my control. All I can do is ask via the prescribed management interfaces. Peter -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Paul Gilmartin Sent: Wednesday, November 08, 2017 2:15 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Are JZOS JVM loader excutables installed in PDSE libraries? On Wed, 8 Nov 2017 18:50:28 +, Farley, Peter x23353 wrote: >Thanks Andrew and Allan for the confirmation and install doc link. I can use >those to prompt our systems team to "do the right thing" with JZOS. Isn't "the right thing" to install using SMP/E? -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Are JZOS JVM loader excutables installed in PDSE libraries?
On Wed, 8 Nov 2017 18:50:28 +, Farley, Peter x23353 wrote: >Thanks Andrew and Allan for the confirmation and install doc link. I can use >those to prompt our systems team to "do the right thing" with JZOS. > Isn't "the right thing" to install using SMP/E? -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Are JZOS JVM loader excutables installed in PDSE libraries?
Understood, and I have done that for a POC, but this needs to be available shop-wide going forward, so I will engage our systems team about it. Peter -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Andrew Rowley Sent: Wednesday, November 08, 2017 1:59 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Are JZOS JVM loader excutables installed in PDSE libraries? You can also allocate your own PDS/E and copy it there for your own use via STEPLIB. It doesn't need linklist or APF. On 08/11/2017 06:50 PM, Farley, Peter x23353 wrote: > Thanks Andrew and Allan for the confirmation and install doc link. I can use > those to prompt our systems team to "do the right thing" with JZOS. > > Peter > -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Are JZOS JVM loader excutables installed in PDSE libraries?
You can also allocate your own PDS/E and copy it there for your own use via STEPLIB. It doesn't need linklist or APF. On 08/11/2017 06:50 PM, Farley, Peter x23353 wrote: Thanks Andrew and Allan for the confirmation and install doc link. I can use those to prompt our systems team to "do the right thing" with JZOS. Peter -- Andrew Rowley Black Hill Software -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Are JZOS JVM loader excutables installed in PDSE libraries?
Thanks Andrew and Allan for the confirmation and install doc link. I can use those to prompt our systems team to "do the right thing" with JZOS. Peter -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Allan Staller Sent: Wednesday, November 08, 2017 1:44 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Are JZOS JVM loader excutables installed in PDSE libraries? I just recently installed maint for JAVA (V7 and V8). The JVM* modules were copied to SYS1.SIEALNKE. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Andrew Rowley Sent: Wednesday, November 8, 2017 11:59 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Are JZOS JVM loader excutables installed in PDSE libraries? On 07/11/2017 09:00 PM, Farley, Peter x23353 wrote: > So my installation question is this: Does the normal installation of the > JZOS component also include automatic copying of the JVMLDMxx executable(s) > into some system-maintained PDSE(s)? > > If not, where is it documented how to copy these executable(s) into a PDSE > library which can legally be used as a STEPLIB, and that it is the user's > responsibility to do this in order to use JZOS? > > The JZOS installation documentation is available here: ftp://public.dhe.ibm.com//software/Java/Java80/JZOS/jzos_users_guide_v8.pdf I think a SMP/E installation should put the modules in SYS1.SIEALINKE. You need to manually copy them for a non-SMP/E installation (probably not to SYS1.SIEALINKE, although that is what the doc suggests). -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Are JZOS JVM loader excutables installed in PDSE libraries?
I just recently installed maint for JAVA (V7 and V8). The JVM* modules were copied to SYS1.SIEALNKE. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Andrew Rowley Sent: Wednesday, November 8, 2017 11:59 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Are JZOS JVM loader excutables installed in PDSE libraries? On 07/11/2017 09:00 PM, Farley, Peter x23353 wrote: > So my installation question is this: Does the normal installation of the > JZOS component also include automatic copying of the JVMLDMxx executable(s) > into some system-maintained PDSE(s)? > > If not, where is it documented how to copy these executable(s) into a PDSE > library which can legally be used as a STEPLIB, and that it is the user's > responsibility to do this in order to use JZOS? > > The JZOS installation documentation is available here: ftp://public.dhe.ibm.com//software/Java/Java80/JZOS/jzos_users_guide_v8.pdf I think a SMP/E installation should put the modules in SYS1.SIEALINKE. You need to manually copy them for a non-SMP/E installation (probably not to SYS1.SIEALINKE, although that is what the doc suggests). -- Andrew Rowley Black Hill Software -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Are JZOS JVM loader excutables installed in PDSE libraries?
On 07/11/2017 09:00 PM, Farley, Peter x23353 wrote: So my installation question is this: Does the normal installation of the JZOS component also include automatic copying of the JVMLDMxx executable(s) into some system-maintained PDSE(s)? If not, where is it documented how to copy these executable(s) into a PDSE library which can legally be used as a STEPLIB, and that it is the user's responsibility to do this in order to use JZOS? The JZOS installation documentation is available here: ftp://public.dhe.ibm.com//software/Java/Java80/JZOS/jzos_users_guide_v8.pdf I think a SMP/E installation should put the modules in SYS1.SIEALINKE. You need to manually copy them for a non-SMP/E installation (probably not to SYS1.SIEALINKE, although that is what the doc suggests). -- Andrew Rowley Black Hill Software -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: C/C++ Runtime Library
Frank Swarbrick wrote: Doesn't that make for fairly large executables? Well - it can - but a trimmed down C library is surprisingly small. Of course - if you're dragging C++ into this, then things get bigger; but again - that's not the library usually, it's the templates, etc.. that your program instantiates... It seems, in practice, to not be an issue at all. - Dave Rivers - Let me also speak as a vendor; for Dignus C/C++ (in he default mode of operation) the runtime is linked with the program. There is no dependency on an externally loaded component - or LE. So, you don't have to worry about version compatibility. - Dave Rivers - -- -- riv...@dignus.comWork: (919) 676-0847 Get your mainframe programming tools at http://www.dignus.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: PCOMM macro/script - Copy Screens, Copy Append
We've used Passport for several years. Here's a VBScript example for Passport that will allow you to specify the number of screens you want to copy and optionally the beginning and ending row on the screen. After it copies each screen and appends it to a temporary file, it invokes my editor so that I can see the whole capture. Comments start with a single quote. At the end there is another way of doing this using VBScripts FileScriptingObject (FSO). Passport had some issues with a 60x100 screen that way, so I stayed with the first version. But maybe it matches PCOMM's functions better. At least it shows how to work with FSOs. The macrouses Passport functions: GetScreenSize AppendPSToFile SendHostKeys WaitForHostUpdate And the VBScript functions: MsgBoxGetInput Shell I have the macro assigned to CTRL-S in my Passport keyboard so that I can just press Ctrl-S and be prompted for the number of pages, begin row & end row on each screen. It saves the screen & pages down that number of times, then starts my editor with the results in the C:\temp file. - Wendell Lovewell ' *** ' This macro will page through a TRACK or XRAY storage display (D dataname or A address) ' and copy the number of pages you supply into a file named c:\temp\text.txt ' Assigned to Alt-D Sub ZMain() Dim Text, ret, nTimes, K, L, wrk, wrk2, wrk3 Dim strText Dim nScreenSize, nRows, bRow, eRow, nCols nScreenSize = GetScreenSize If nScreenSize = 3564 Then nrows = 27 if nScreenSize = 3440 Then nrows = 43 if nScreenSize = 2560 Then nrows = 32 if nScreenSize = 1920 Then nrows = 24 if nScreenSize = 7200 Then nrows = 60 bRow = 7 eRow = nRows - 2 nCols = 80 If nScreenSize = 7200 Then ncols = 69 ret = Shell("c:\util\rm.bat C:\Temp\test.txt",6)' Call BAT file to delete previous version of the file strText = "Screen Size = " & nScreenSize & " - " & nRows & " rows" & vbCRLF strText = strText & "Enter the number of screens to copy, optionally with ',bRow,eRow'" nTimes = MsgBoxGetInput (strText) K = InStr(nTimes,"*") If K > 0 Then L = K - 1 nTimes = Left(nTimes,L) bRow = 1 eRow = Nrows End If K = InStr(nTimes,",") If K > 0 Then L = K - 1 wrk2 = nTimes 'temp hold nTimes in wrk2 nTimes = Left(nTimes,L) L = K + 1 wrk = Mid(wrk2,L) 'wrk = part after nTimes, K = Instr(wrk,",") 'Is there a comma? If K > 0 Then L = K - 1 bRow = Mid(wrk,l,1) l = k + 1 wrk = Mid(wrk,l) 'wrk now = part after 2nd "," If Trim(wrk) > "" Then eRow = Trim(wrk) Else eRow = NRows End If End If End If '*** ' Now, copy the data to the file via Passport's AppendPSToFile function for k = 1 to nTimes Ret = AppendPSToFile("c:\temp\test.txt",bRow,2,eRow,ncols) SendHostKeys ("") ret = WaitForHostUpdate(3) Next '*** If bRow = 7 Then ret = Shell("c:\util\x.bat C:\Temp\test.txt ( PROFILE CopyDumpToFPE",1) Else ret = Shell("c:\util\x.bat C:\Temp\test.txt",1) End If End Sub ' '** ' ' This is close to working, but also hung on the 60 x 100 screen size ' ' Needs crlf at end of each line ' ' Sub ZMainDidnotwork() ' Dim Text, ret, nTimes, k ' Dim strText, nRet ' Dim nCursorRow ' Dim nScreenSize, nRows, strCopyArea, EndRow, nBytes ' ' ' nCursorRow = GetCursorRow ' ' strText = "Current row position = " & nCursorRow ' ' ' nRet = MsgBox (strText, 0, "Row Position") ' ' nScreenSize = GetScreenSize ' If nScreenSize = 3564 Then nrows = 27 ' if nScreenSize = 3440 Then nrows = 43 ' if nScreenSize = 2560 Then nrows = 32 ' if nScreenSize = 1920 Then nrows = 24 ' if nScreenSize = 7200 Then nrows = 60 ' EndRow = nRows - 2 ' ' strText = "Screen Size = " & nScreenSize & " - " & nRows & " rows" & vbCRLF ' strText = strText & "Enter the number of screens to copy" ' nTimes = MsgBoxGetInput (strText) ' ' strCopyArea = "" ' nBytes = (Nrows - 6 - 2) * 80 ' ' for k = 1 to nTimes 'Ret = SelectArea(7,1,nRows,80) 'strCopyArea = StrCopyArea & GetString (7,1,nBytes) ' 'SendHostKeys ("") 'ret = WaitForHostUpdate(5) 'Next ' ' strText = "The length of the data copied is " & Len(StrCopyArea) ' ret = MsgBox (strText,0,"Bytes Copied") ' ' ret = Shell("c:\util\rm.bat C:\Temp\CopyDump.txt",6) ' Call PutString (strCopyArea) ' ret = Shell("c:\util\x.bat C:\Temp\CopyDump.txt",1) ' End Sub ' ' ' Function PutString(fileText) ' ' Const ForReading = 1, ForWriting = 2 ' ' Dim fso, MyFile, FileName, FileContents, pwd, t ' ' Set fso = CreateObject("Scripting.FileSystemObject") ' ' FileName = "C:\temp\CopyDump.Txt" ' ' ' Open the file for output. ' ' ' Open the file for input. ' Set MyFile = fso.CreateTextFile(FileName, True) ' ' MyFile.Write FileText ' ' If ret
Re: Are JZOS JVM loader excutables installed in PDSE libraries?
On Wed, 8 Nov 2017 08:01:48 -0600, John McKown wrote: > >> o Concatenated UNIX directories in Binder SYSLIB. > >This last will likely be rejected as "not needed". Why? You can use >multiple UNIX directories for AUTOCALL as in the following (SYSLIN binder >input) > >//SYSLIN DD * > AUTOCALL /some/directory/obj > AUTOCALL /another/directory/obj > AUTOCALL /some/directory/archive-library.a > LIBRARY <-- can't figure this one out --> >/* > Are these the implementation of the various options to "cc"? You might experiment, generating the pseudo-JCL. >When you use the AUTOCALL, I'm not sure what the file name needs to be in >the specified directory. For instance for an external reference to MYPROG, >would the file name be MYPROG or myprog or myprog.o? There are _no_ >examples of this in the manual. The same in an archive library. And I'm >working from home today, which "cramps my style" for messing around testing >UNIX stuff. > For INCLUDE it's "INCLUDE ddame(myprog.o)" (No 8-character limit.) Does AUTOCALL interact with INCLUDE or is it solely for resolving EXTERNs? >Ref: >https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieab100/autocal.htm >https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieab100/library.htm -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Are JZOS JVM loader excutables installed in PDSE libraries?
On Tue, Nov 7, 2017 at 4:47 PM, Paul Gilmartin < 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > On Tue, 7 Nov 2017 21:00:41 +, Farley, Peter x23353 wrote: > > > >As Gil has pointed out several times, you cannot *legally* use a Unix > directory in a STEPLIB DD or concatenation (well, anyway it is not > documented that you can). And in fact although this may occasionally work > with an empty PDS(E) as the first catenand, ... > > > I believe I was whining about SYSEXEC, not STEPLIB. I've never tried the > latter. > > > my experience of trying this with the JZOS loader executables is that it > generates an S922 abend (fatal error in initiator, SVC dump taken). > > > And Binder very explicitly prohibits catenation of UNIX directories > in SYSLIB; they must be singletons. The Ref. pretty much states > that Binder performs no search of a UNIX SYSLIB, rather it extracts > the SYSLIB path (SVC 99?) and appends the member name. (The > Ref. neglects to mention an intervening '/'.) > > Three grists for the RFE mill: > o UNIX directories in SYSEXEC. > o UNIX directories in STEPLIB. (How about //PDSE in PATH!?) > o Concatenated UNIX directories in Binder SYSLIB. > This last will likely be rejected as "not needed". Why? You can use multiple UNIX directories for AUTOCALL as in the following (SYSLIN binder input) //SYSLIN DD * AUTOCALL /some/directory/obj AUTOCALL /another/directory/obj AUTOCALL /some/directory/archive-library.a LIBRARY <-- can't figure this one out --> /* When you use the AUTOCALL, I'm not sure what the file name needs to be in the specified directory. For instance for an external reference to MYPROG, would the file name be MYPROG or myprog or myprog.o? There are _no_ examples of this in the manual. The same in an archive library. And I'm working from home today, which "cramps my style" for messing around testing UNIX stuff. Ref: https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieab100/autocal.htm https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieab100/library.htm > > -- gil > > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: What cryptographic algorithm is not supported?
I notice your cert display did not list a "Key Usage" section. X509v3 Key Usage: critical Digital Signature, Key Encipherment, Data Encipherment Digital Signature and Data Encipherment are defaults, but KeY Encipherment does not default and needs to be specified in Key Usage. X509v3 extensions: X509v3 Basic Constraints: CA:FALSE X509v3 Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication Netscape Comment: OpenSSL Generated Certificate 82:7D:1F:EF:53:DB:3D:E1:14:62:03:49:34:16:A2:92:D9:46:51:1E > Sent: Tuesday, November 07, 2017 at 10:40 AM > From: "Charles Mills"> To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: What cryptographic algorithm is not supported? > > That could be another thread "most useless diagnostic ever." > > Right, that is the API call (apparently) that failed, but I don't think one > knows that just from the error message. As I said, I got the same error > message for presenting a certificate with a SHA-1 digest (I think). > Presumably a different CMS API call but the same external message. Different > action for the user. > > I display certificates all the time. My script that issues OpenSSL > certificates displays them at the end. > > Charles > > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Kirk Wolf > Sent: Tuesday, November 7, 2017 8:07 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: What cryptographic algorithm is not supported? > > Its not the worst diagnostic situation that I have seen on z/OS ( that award > would go to the C-library OS I/O stuff IMO). > > In this case, the external API that failed is gsk_decode_import_key(), and if > you look it up the error that you are getting is documented: > https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.gska100/msg34.htm > > The algorithm codes can be found in /usr/include gskcms.h > x509_alg_pbeWithSha1And40BitRc2Cbc = 36, /* 1.2.840.113549.1.12.1.6 */ > > Kirk Wolf > Dovetailed Technologies > http://dovetail.com > > PS> If you want some "fun", take you X.509 cert and load it into a > PS> ASN.1 > tool that displays the whole ugly thing > > -- > 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