CQE Queue Registration Guide

Learn how to register a CQE (Custom Query Engine) script as an execution schedule on one or more logical servers (LSSN), and what timezone rule applies to the start date.

🚀 Go to CQE Queue Registration →

📋 Overview

CQE Queue Registration lets you pick a script (mssn) from the repository, choose the logical servers (lssn) that should run it, and register it as an execution schedule (tMgmtScriptList). After a successful save, you are taken to the CQELSVR Run List screen.

🕒 Start date timezone rule — please read

Aspect	Basis
Input / display on screen	Your browser's local time (KST in Korea, JST in Japan, and so on)
Transmission / storage	UTC (ISO 8601). The screen converts it automatically right before sending.

• Type the time exactly as it reads on the machine you are working on. You do not need to work out the UTC offset yourself.
• The moment you press Save, the screen converts local time to UTC and sends that. The database records the UTC value.
• That is why columns such as lastdate on the CQELSVR Run List are shown on a UTC basis. A difference equal to your timezone offset is expected and correct.

A start date in the future means it will not run until then

The start date means "do not run before this instant". If you set a future time, no agent will pick the schedule up until that time arrives. If you want it to run right now, leave the start date at the current time (or a past time). The field is pre-filled with the current local time when the page opens, so for immediate execution you can simply leave it alone.

⚠️ Previously the screen sent the local wall-clock string with no UTC conversion, so a time that was offset hours in the future got stored in the UTC database (giip #2537). Such a schedule was permanently pushed to the back of the pickup ordering and never ran at all. The screen now owns the conversion.

🔍 Screen Layout

1. Script selection (mssn)

• mssn input: type the unique ID of the script to run.
• Select button: opens a popup listing the script repository for the current project (csn). You can search by keyword and page through with Prev / Next; pressing Select on a row fills in both mssn and script type automatically.
• This field is required — the form will not save while it is empty.

2. Target server selection (LSSN Group)

• The logical servers registered under the current project (csn) are listed as checkboxes, shown as LSSN — usage @ hostname.
• You can select several servers at once; a schedule is registered for each selected server.
• At least one server must be selected before saving.

3. Execution options

• csn: project number. Filled in automatically from your login session.
• interval: repeat interval, in minutes.
• active: whether the schedule is enabled. If off, it is registered but will not run automatically.
• script type: the script's type (filled in automatically when you pick a script).
• repeat: whether the schedule repeats. Turn it off for a one-off schedule.
• startdate: the start date/time (YYYY-MM-DD HH:mm). See the "Start date timezone rule" section above.
• auid: the requesting user ID. Defaults to the user ID of your login session.

4. Custom values (custom_values)

Use this when you want to run the original script with different values without editing the script itself. Whatever you type here replaces the {{customvalues}} placeholder inside the original script body.

5. Save / Cancel

• Save: validates the form, registers the queue entry, and navigates to the CQELSVR Run List.
• Cancel: returns to the run list without registering anything.

⚙️ Requirements

• Requires a logged-in session (CSN) — without one, neither the server list nor the script list can be loaded.
• Both the script (mssn) and the servers (lssn) you register must belong to the current project.

Troubleshooting

Symptom	Cause	Resolution
The LSSN Group list is empty	No logical servers are registered under the current project (csn), or the session expired	Confirm the correct project is selected at the top, and log in again if necessary.
"mssn is required" error	Save was pressed without picking a script	Use the Select button to choose a script from the repository.
"At least one LSSN must be selected" error	No target server was checked	Check at least one server in the LSSN Group list.
"Start date: use YYYY-MM-DD HH:mm or ISO format" error	The start date could not be parsed	Re-enter it as 2026-09-15 14:30. Leaving it blank is also allowed.
After saving, lastdate in the run list differs from what you typed	lastdate is displayed on a UTC basis while your input was local time	This is expected — the difference equals your timezone offset.
It is registered, but no agent picks it up after several minutes	The start date was set in the future, or active is off	Check the start date and re-register with the current time if you need immediate execution. Also confirm active is on.

🔌 CQE API (for automation)

This screen's actions map to the following CQE API verbs (byAK/bySk dispatcher). Requests send text (verb + parameter names), jsondata (values), and token.

• CQEQueuePut mssn lssngroup csn interval active script_type custom_values repeat startdate auid — registers a schedule on each of the selected servers (lssngroup, comma-separated). startdate must be a UTC ISO 8601 string (for example 2026-09-15T05:30:00.000Z). Sending a local wall-clock string stores a future time in the database, and the schedule will never run.
• CQERepoList csn <offset> [N'keyword'] — lists the repository entries shown in the script picker popup (15 rows per page).
• LSVRList csn — lists the logical servers registered under that project (used by the LSSN Group checkboxes).

Auth model: this page's API does not use the giip-issue skill's x-api-key (SK) model — it uses the logged-in session's token model, sending user_id + token with each request.

Full specification for adjacent features: CQELSVR Run List Guide, CQE Repository Script Management Guide, and giipdb docs/30_Specs/CQE_SPECIFICATION.md.

---

Version: 1.0 Last Updated: 2026-09-15 Source File: giipv3/public/help/cqeQueuePut.en.md