Loading ...
Sorry, an error occurred while loading the content.
 
  • Back
  • About Group

  • Join Group
, added in the last 7 days
New MessagesSee All
  • Re: MVS/380 2.0 - the next generation

    ... And for completeness - the exit is entered with the DCB address in the low three bytes, and the open flags in the high byte, so that has to be either saved

    gerhard_postpischil_swrx 3 days ago
  • Re: MVS/380 2.0 - the next generation

    ... Thus there is no different code path for z/OS, so no testing of the environment using CVT or whatever is required. When we have the technology to load a

    kerravon86 4 days ago
  • Re: MVS/380 2.0 - the next generation

    ... Just for the sake of anyone watching, here is the code that PDPCLIB uses to allow a module to reside ATL without using a DCBE for the DCB open exit (and

    kerravon86 4 days ago
Fetching Sponsored Content...

Group Description

Discussion of everything related to the OS/380 family of operating systems (MVS/380, VM/380, VSE/380), the hardware it runs on (S/380), the software that emulates that hardware (Hercules/380), the applications that run on those operating systems (GCCMVS, PDPCLIB, BREX, DIFFUTILS) - both use of and design of all components, which are expected to mature together. Also maintenance and distribution of same. Also any of these products being used on their big brothers (z/OS, z/VM, z/VSE).

Group Information

Group Settings

  • This is a restricted group.
  • Attachments are permitted.
  • Members cannot hide email address.
  • Listed in Yahoo Groups directory.
  • Membership requires approval.
  • Messages are not moderated.
  • All members can post messages.

Message History