of GDGs is to be able to address all generations simultaneously within a JCL script without having to know the number of currently available generations. To do this, you have to omit the parentheses and the generation number in the JCL when specifying the dataset. Example Creation of a standard GDG for five safety scopes, each at least 35 days old: //STEP1 EXEC PGM=IDCAMS //SYSPRINT DD SYSOUT=* //SYSIN DD * DEFINE GDG (NAME('DB2.FULLCOPY.DSNDB04.TSTEST') LIMIT(5) SCRATCH FOR(35)) /* Delete a standard GDG: //STEP3 EXEC PGM=IDCAMS //SYSPRINT DD SYSOUT=* //SYSIN DD * DELETE DB2.FULLCOPY.DSNDB04.TSTEST GDG FORCE /* Operational data collection and analysis Operational data is data that z/OS system produces when it runs. This data indicates the health of the system and can be used to identify sources of performance and availability issues in the system. IBM Z Operational Log and Data Analytics and IBM Z Anomaly Analytics with Watson collect IT operational data from z/OS systems, analyze and provide insights about the operational data. IBM Z Operational Log and Data Analytics collects IT operational data from z/OS systems, transforms it to a consumable format, and streams it to third-party enterprise analytics platforms like the Elastic Stack and Splunk, or to the included operational data analysis platform. The included insights can help to visualize and search operational data to help identify the cause of operational issues. IBM Z Anomaly Analytics with Watson collects IT operational data from z/OS systems, uses historical IBM Z metric and log data to build a model of normal operational behavior, then analyzes real-time operational data through comparison with the model of normal operations to detect anomalous behavior, and notifies IT operations of the anomalous behavior to identify incidents that might lead to business disruption. Operational data types IBM Z Operational Log and Data Analytics collects and analyzes both structured and unstructured data, including the following types of operational data: System Management Facilities (SMF) data Log data from the following sources: Job log, the output which is written to a data definition (DD) by a running job z/OS UNIX log file, including the UNIX System Services system log (syslogd) Entry-sequenced Virtual Storage Access Method (VSAM) cluster z/OS system log (SYSLOG) IBM Tivoli NetView for z/OS messages IBM WebSphere Application Server for z/OS High Performance Extensible Logging (HPEL) log z/OS Resource Measurement Facility (RMF) Monitor III reports User application data, the operational data from users' own applications IBM Z