> 192 prefixed IP addresses are class C addresses > https://en.wikipedia.org/wiki/Classful_network. That's a deprecated term. Since this introduction of cidr addresses there really aren't classes of addresses anymore. The only special 192.x.x.x addresses are the private space as has been mentioned.
> It's a bit disconcerting that github is being blocked because IBM (and the > company I work for) are using github to ship code and add-ons for our > products. All the new Liberty server goodies from IBM are staged in github > repositories. > I don't understand why a company would block a site that hosts source code > repositories. Has there been a major security issue browsing github that > compromises clients? > Companies are restricting sites where people can download and then presumably install software. Obviously there are many small sites that allow this, but GitHub and some others are huge and only provide this service. So they are low hanging fruit. Unauthorized installing of software is a huge malware installation vector and it can also have licensing issues for the company. So usually it's a no no at bigger companies. Chad >> I can reach gist from home though, maybe you can as well. >> >> Peter >> >> -----Original Message----- >> From: IBM Mainframe Discussion List [mailto:[email protected]] On >> Behalf Of Steve Coalbran >> Sent: Friday, March 04, 2016 5:56 AM >> To: [email protected] >> Subject: Re: rexx and tso alllocate >> >> Hi Lizette - this site gets forbidden for me (I work for Nordea bank now - >> no longer IBM - more restrictive) >> Could you possibly be so kind as to send me this code :-D to >> [email protected] ? >> /Steve >> >>> Date: Thu, 3 Mar 2016 10:27:28 -0700 >>> From: [email protected] >>> Subject: Re: rexx and tso alllocate >>> To: [email protected] >>> >>> Have you tried under TSO BATCH with or without ISPF libraries (and I am >>> thinking the ISF libraries may need to be included in the JCL). >>> >>> Lizette >>> >>> >>> -----Original Message----- >>>> From: "Barkow, Eileen" <[email protected]> >>>> Sent: Mar 3, 2016 9:26 AM >>>> To: [email protected] >>>> Subject: Re: rexx and tso alllocate >>>> >>>> I am currently converting some SDSF BATCH routines to SDSF REXX and I am >>>> finding that things do not always work the same when >>>> invoking the clist from ISPF 1.6 and invoking it from batch with IRXJCL. >>>> option 1.6 runs under TSO/E and IRXJCL does not. >>>> so far, I have encountered differences with the ISFOWNER settings, putting >>>> quotes on datasetnames used for ISFPRTDSNAME, >>>> and the use of the TSO/E SYSDSN routine is not allowed with IRXJCL. >>>> >>>> -----Original Message----- >>>> From: IBM Mainframe Discussion List [mailto:[email protected]] On >>>> Behalf Of Lizette Koehler >>>> Sent: Thursday, March 03, 2016 11:09 AM >>>> To: [email protected] >>>> Subject: Re: rexx and tso alllocate >>>> >>>> If you search on JES2DISK by John McKown, >>>> https://gist.github.com/JohnArchieMckown/b27747d0c4750a258997 >>>> >>>> This is a very nice example of extracting from SPOOL to DASD or other. >>>> >>>> Lizette >> -- >> >> 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 [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
