Skeleton SQL statement to set the “next expected” date and time - syncsort_capacity_management - Latest

Syncsort™ Capacity Management Guide

Product type
Software
Portfolio
Integrate
Product family
Syncsort™ Software
Product
Syncsort™ Capacity Management
Version
Latest
Language
English
Product name
Syncsort™ Capacity Management
Title
Syncsort™ Capacity Management Guide
Copyright
2024
First publish date
1985
Last edition
2024-08-06
Last publish date
2024-08-06T15:42:28.602035
UPDATE [dbo].[s_TargetStatistics]
SET GatekeeperNextExpected = {ts '<YYYY-MM-DD HH:MM:SS>'}
FROM [dbo].[s_TargetStatistics] TS
INNER JOIN [dbo].[s_Target]T
ON T.TargetID = TS.TargetID
WHERE TS.LastGatekeeperStatus = 0 AND T.TargetTypeID = 8
AND T.TargetName = '<TargetName>'

 

You can use SQL Server Management Studio to run this statement. Before executing, you should:

  • Check you are pointing to the correct SQL Server database.

  • Replace <YYYY-MM-DD HH:MM:SS> (including the brackets) with the date and time where the Gatekeeper is to start checking once more; for example, 2019-01-07 02:45:00.

  • Replace <TargetName> (including the brackets) with the name of the Target for which you want to have Control Center allow one or more gaps in data. If this database is using a case-sensitive schema you must make sure you match exactly the capitalization of the name; for example, zOS Production. If you are not sure whether the database is case-sensitive, set­ting the exact name will do no harm one way or the other.

The SQL statement here will not update the GatekeeperNextExpected value unless the tar­get:

  • Is a z/OS target

  • Is currently in a state where the Gatekeeper has suspended the collection

If the SQL statement is unsuccessful the following statement will show in the Messages window:

(0 rows affected)

 

If the GatekeeperNextExpected field for the Target has been updated successfully the following statement will show in the Messages window:

(1 row affected)