Customer decided to make the change as usual it means hard coding the new VAT, for future changes they want to have a best mechanism. I appreciate all the information and suggestions you all provided here, certainly will be explored, analised and thoroughly tested before to be implemented.
Thanks to all. 2017-01-04 7:17 GMT-05:00 Elardus Engelbrecht < [email protected]>: > Windt, W.K.F. van der (Fred) wrote: > > >> Can COBOL read environment variables these days? > > >You can call CEEGTJS to read the value of (exported) JCL variables. > > Indeed. It is more or less the same as other LE functions + services like > CEEENV, CEEDATE, CEEBLDY, CEE3PRM, CEEGMT, CEESxLOG, etc. You setup the > parameters, storage, etc and way how you call it and then you call that > function/service. [1] > > In fact, the book (z/OS Language Environment Programming Reference) > contains C++ and COBOL examples for these functions and callable services. > Hard and difficult RTFM work, of course, but once you got the hang, it > should be easy. > > This book only contains an example CEEGTJS in C/C++, but it should not be > that hard to do the same in COBOL or PL/I. Hmmm, perhaps in a good rainy > day, I should try out that CEEGTJS in COBOL out just for fun. ;-) > > Just keep an eye on these results after calling that service CEEGTJS: > CEE000, CEE3L9, CEE3LA, CEE3QS > > Groete / Greetings > Elardus Engelbrecht > > [1] - I played around in Assembler and COBOL with date/time/utc/local CEE > functions during testing and implementing of our brand new STP some years > ago. > > ---------------------------------------------------------------------- > 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
