Memunic Chronicles in Atomic Arena

Recently I was working for a client who didnt have JSCAN/JEM to expand and do syntax/dataset xref checking of a JCL before actually submitting it. As You would understand as a developer how useful it is to have such a utility. And this prompted me to create the JCLEXP tool which checks for things like dataset existance, symbolic parameters expansion, PROCs and Include Members Expansion, Sysin's or other Parm Files Existance etc. Note that the tool doesnot do a JCL syntax check.  You can View/Edit/Browse files directly or using Fileaid directly from the tool's output panel. You can get a list of all input and output files used in the job. You can resolve the actual GDG version dataset going to be used in the job. Most importantly You can see the errors that the job has in its cross references with other modules/datasets. In a nutshell this Exec Reads in the i/p JCL and Expands the Includes, Procs, Symbolic variables in the Job. It also scans for any Datasets, GDG Base...

Earlier   distributed   systems   suffered   from   interoperability   issues because  each  vendor  implemented  its  own  on-wire  format  for  distributed  object messaging.  By  using  XML  as  an  on-wire  standard,  the  two  camps  of  Java/J2EE and .NET/C# now could speak to each other.  Extensible Markup Language (XML) is a extensible,   portable,  and  structured  text  format.  XML  is  playing  an  increasingly important role in the exchange of a wide variety of data on the Web and elsewhere. Need of XML in COBOL: With   the   latest   advances   in   mainframe   SOA   technology,  the mainframe is rapidly evolving into an industry standard server, capable of publishing legacy  data and applications as Web services, as well as co...