Hi Andrew. Thanks for your explanations.
When I corrected the json file I specified in the CREDSNAM DD *, the step ended
with RC=0. It returned
5695-DF124 DFSMSdfp CDA 3.2 CLOUD OBJECT UTILITY 2026141 12:17:55
CREDENTIALS(ADD) PROVIDER(AZURE)
GDKU0013I CREDSNAM: /usr/lpp/dfsms/gdk/tempkeys.json
GDKU0030I BUCKET NAME NOT SPECIFIED FOR CREDS(ADD) COMMAND. CREDENTIALS WILL BE
SAVED AS DEFAULT CREDENTIALS
GDKU0100I CREDENTIALS(ADD) PROCESSING SUCCESSFUL
It also added a new MVSUSER section in the gdkkeyf.json file for the user. But
the section didn't have "key" or "secretkey" pairs:
"MVSUserID": "WXYZ",
"cloud provider": {
"AZURE": [
{
"keylabelID": "A00000",
"name": "/",
"NoCEX": "true",
"timestamp": "2026-05-21 12:17:55"
}
]
}
Did those go in "DEFAULT CREDENTIALS"? Where are those stored?
A subsequent LIST function from that user failed with
GDKU0101E ERROR DURING LIST REQUEST. GDKRC=114: Invalid authorization parameters
(Just an aside, the timestamp is in GMT time, as are the timestamps for members
I upload to a PDS. Do you happen know where that is set? Most everything else
is local time, including the timestamps for the changed dates for USS files.)
Thanks again for your help!
Wendell
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
