Joined: 22 Apr 2006 Posts: 6258 Location: Mumbai, India
AFAIK, as an Application programmer you can't do this unless you change your IEBGENER Jobs to explictly call ICEGENER. If I got your question correctly, this is done by your System Programmers at the time of installation. Having said that, not every job written in IEBGENER can be converted to ICEGENER - if the function is enabled during installation, it'll get evaluated if for the copy operation ICEGENER should be invoked or IEBGENER.
ICEGENER is a product from IBM (DFSort), if your shop is a DFSORT shop, you'll see ICExxxx messages in SYSOUT, however, if the shop is Sync-Sort shop SyncGENER will be invoked under the covers and you'll see SYTxxxx messages.
If ICEGNER is more effecient than IEBGENER for copying, how can we make out that ICEGNER is invoked when IEBGENER is called if the site has chose this option.
Can this be known by some messages or logs?
Remember that ICEGENER is invoked only for qualifying IEBGENER jobs that are processed by the equivalent (though not identical), but more efficient, DFSORT copy function. If, for any reason, the DFSORT copy function cannot be used (for example, if IEBGENER control statements are specified), control is automatically transferred to the IEBGENER system utility.
Assuming your shop has DFSORT, you can check the SYSPRINT dd for messages beginning with ICExxx and you will know that you invoked DFSORT's ICEGENER for the copy job.