Tom at 22:21, 3 November 2026

2026-11-03T22:21:01Z

← Older revision		Revision as of 22:21, 3 November 2026
Line 15:		Line 15:

	== Step 1: Get the CPU ID from the customer ==		== Step 1: Get the CPU ID from the customer ==
	~~Only~~ the '''~~rightmost~~ 8 ~~or 10 hexadecimal characters~~''' of the ~~CPU ID are used~~.		The authorization code uses only the '''8-hex-digit CPU serial number'''. The surrounding bytes are ignored: the leading <code>FF</code>/<code>00</code> flag, the following LPAR byte (for example <code>04</code>), and the trailing four digits. The LPAR is not inspected by the authorization code.

	{\| class="wikitable"		{\| class="wikitable"
	! System !! Command !! Example response !! Value to use		! System !! Command !! Example response !! Value to use
	\|-		\|-
	\| z/VM \|\| <code>CP Q CPUID</code> (from the virtual machine that will run the products) \|\| <code>CPUID = FF04686420030000</code> \|\| <code>~~6420030000~~</code> or <code>~~20030000~~</code>		\| z/VM \|\| <code>CP Q CPUID</code> (from the virtual machine that will run the products) \|\| <code>CPUID = FF04686420030000</code> \|\| <code>68642003</code> (<code>FF</code> flag, <code>04</code> LPAR, serial, <code>0000</code>)
	\|-		\|-
	\| z/OS (MVS, OS/390) \|\| <code>D M=CPU</code> (operator or SDSF console with command authority) \|\| SERIAL column: <code>0468642003</code> \|\| <code>~~0468642003~~</code>		\| z/OS (MVS, OS/390) \|\| <code>D M=CPU</code> (operator or SDSF console with command authority) \|\| SERIAL column: <code>0468642003</code> \|\| <code>68642003</code> (the leading <code>04</code> LPAR prefix may be omitted)
			\|-
			\| z/VSE \|\| <code>SIR</code> command \|\| <code>AR 0015 CPUID VM = 00379B7891758000 VSE = FF379B7891758000</code> \|\| <code>9B789175</code> (use either the VM or VSE value; <code>37</code> is the LPAR)
	\|}		\|}

	~~CPU IDs must be~~ 8 or 10 hex digits. A 10-digit ID is compared to existing customers using its rightmost 8 digits.		The maintenance site accepts 8 or 10 hex digits. A 10-digit value (LPAR byte plus serial, as z/OS shows it) is compared to existing customers using its rightmost 8 digits, so entering the 8-digit serial is simplest.

	== Step 2: Find or add the customer ==		== Step 2: Find or add the customer ==

Tom: Created page with "NOINDEX NOTOC
'''Internal use only.''' This page is intentionally not linked from the main page or any category. Do not link it from customer-facing pages.
= Creating Model 204 authorization keys (internal) = Model 204 products are licensed per CPU. An authorization key (also called an ''authorization zap'' or ''AUTH zap'') is generated on demand by the Rocket maintenance subsystem (the `maint` p..."

2026-11-03T22:12:12Z

Created page with "__NOINDEX__ __NOTOC__ <div style="border:1px solid #c00; padding:6px;">'''Internal use only.''' This page is intentionally not linked from the main page or any category. Do not link it from customer-facing pages.</div> = Creating Model 204 authorization keys (internal) = Model 204 products are licensed per CPU. An authorization key (also called an ''authorization zap'' or ''AUTH zap'') is generated on demand by the Rocket maintenance subsystem (the <code>maint</code> p..."

New page

__NOINDEX__
__NOTOC__
<div style="border:1px solid #c00; padding:6px;">'''Internal use only.''' This page is intentionally not linked from the main page or any category. Do not link it from customer-facing pages.</div>

= Creating Model 204 authorization keys (internal) =

Model 204 products are licensed per CPU. An authorization key (also called an ''authorization zap'' or ''AUTH zap'') is generated on demand by the Rocket maintenance subsystem (the <code>maint</code> procedures) and identifies the CPU serial number(s), the start and end dates, the products, and, for thread-based products, the maximum thread count.

Keys are not created by hand. They are built by the maintenance subsystem when an authorized user requests one, either from the web or by e-mail.

== Before you start ==
* You need a maintenance-site login (userid) with access to the customer. Access is checked against the customer nickname; a user who is not authorized for the nickname receives a "401 Unauthorized" response.
* The customer must already exist in the maintenance database (customer record, type ''C'') with its licensed products. To add a new customer, use the ''Add a Customer / Provide CPU IDs'' page (<code>cust1</code>).
* You need the customer's CPU ID(s).

== Step 1: Get the CPU ID from the customer ==
Only the '''rightmost 8 or 10 hexadecimal characters''' of the CPU ID are used.

{| class="wikitable"
! System !! Command !! Example response !! Value to use
|-
| z/VM || <code>CP Q CPUID</code> (from the virtual machine that will run the products) || <code>CPUID = FF04686420030000</code> || <code>6420030000</code> or <code>20030000</code>
|-
| z/OS (MVS, OS/390) || <code>D M=CPU</code> (operator or SDSF console with command authority) || SERIAL column: <code>0468642003</code> || <code>0468642003</code>
|}

CPU IDs must be 8 or 10 hex digits. A 10-digit ID is compared to existing customers using its rightmost 8 digits.

== Step 2: Find or add the customer ==
# Sign on to the maintenance site.
# To check whether a CPU already belongs to a customer, use ''Add a Customer / Provide CPU IDs'' and enter the CPU ID. If it matches an existing customer, you are redirected to that customer's page (<code>dlist?nickname=...</code>); otherwise you can add a new customer.
# Confirm the customer record: nickname, company, operating system, distributor, and the CPU list. Mark test or inactive customers with ''Inactive or Test Client?''.

== Step 3: Request the key ==
# From the customer's page (<code>dlist</code>), choose ''Download authorization keys'' (<code>authlist?nickname=nickname</code>).
# Select the key to build:
#* '''All Authorized Products''' (prefix <code>ALL</code>), which is the normal choice, or
#* a single product, if the customer needs only that one.
# Enter the TCP/IP address (<code>tcpaddr</code>) or e-mail address that should receive the key. ''Email'' links send the key to the address on the customer record.
# Click the download or e-mail link.

Behind the scenes, the web procedure (<code>MAINTP_DOWNLOAD</code>, action <code>GETAUTH</code>) submits a background request of the form:

<pre>AUTH procname prefixAUTH nickname FOR userid [DR cpu[,cpu...]] [DRSTART yyyymmdd]</pre>

The background job builds a temporary procedure named <code>AUTHuserid.time</code>, and the web procedure waits (up to about 100 seconds) for it, then sends it back. The temporary procedures are deleted on the next request by the same user.

== Disaster Recovery (DR) keys ==
A DR key adds temporary authorization for additional CPUs, on top of the CPUs already licensed.
* Enter one or more CPU IDs (8 to 10 hex digits each, separated by commas or blanks) and a start date.
* The start date must be valid, not more than 30 days in the past, and not more than one year in the future. The key is valid for the DR window starting on that date.
* Each customer has a '''DR zap limit''' (<code>DRLIMIT</code>) and a running count (<code>DRCOUNT</code>). If the count would exceed the limit, the request is rejected with "DR ZAP limit ... has been reached, contact Rocket support." To grant more, raise ''Maximum number of DR zaps allowed'' on the customer page.
* The customer page records the start date and CPUs of the most recent DR zap.

== Troubleshooting ==
{| class="wikitable"
! Message !! Meaning / action
|-
| Unauthorized - User ''x'' / Customer ''x'' is not authorized || The userid has no access to that customer nickname. Fix the userid's access.
|-
| CPU ID (...) must be between 8 and 10 hex digits || Bad DR CPU ID. Re-enter it.
|-
| Disaster Recovery test start date is invalid / too old / too far in the future || Correct the DR start date.
|-
| DR ZAP limit ... has been reached || See Disaster Recovery above.
|-
| Not found - No authorization zaps called ... || The key procedure is missing for that product prefix.
|-
| Internal server error - can't build authorization zap || The background build did not finish or returned a result smaller than 500 bytes. Check the maintenance daemon and retry; otherwise escalate.
|}

== Source reference ==
Repository <code>gitm204/maint</code>:
* <code>MAINTP_OBJLIST</code>: the ''Download authorization keys'' page (<code>authlist</code>)
* <code>MAINTP_DOWNLOAD</code>: request validation, DR checks, and the <code>AUTH</code> background request (<code>authSend</code>)
* <code>MAINTP_CUST1</code>: customer maintenance, CPU entry and matching, DR limit fields
* <code>MAINTN_START</code>: routing of the <code>authlist</code> image

Internal:Creating authorization keys - Revision history

Tom at 22:21, 3 November 2026