System_RDR_File_Manage gives "Specified function does not exist"

[Herald ten Dam]

I made the next call:
curl -sk https://10.35.4.60/guests/emp/action -X POST -d '{ "action": "deploy", "image": "IDC_L.1.3.7","vdev": "0200" }' | python -m json.tool

So this is een deployment of a captured image on a existing guest. As a result the function gives an error back:
{'errmsg': "Failed to purge reader of 'EMP'. SMUT error: SMUT request "
           "failed. RequestData: 'changevm EMP purgerdr', Results: '{'rs': "
           "12, 'errno': 0, 'strError': u'ULGSMC5900E Specified function "
           "does not exist', 'overallRC': 8, 'rc': 900, 'response': "
           "[u'(Error) ULTVMU0300E SMAPI API failed: System_RDR_File_Manage, "
           'overall rc: 8, rc: 900, rs: 12, errno: 0, cmd: sudo '
           '/opt/zthin/bin/smcli System_RDR_File_Manage --addRCheader -T EMP '
           "-k spoolids=all, out: API issued : System_RDR_File_Manage', "
           "u'Purge, order, transfer RDR files on target z/VM guest... ', "
           "u'Failed', u' Return Code: 900', u' Reason Code: 12', u' "
           "Description: ULGSMC5900E Specified function does not exist', u' "
           "API issued : System_RDR_File_Manage']}'",
 'modID': 1,
 'output': '',
 'overallRC': 8,
 'rc': 900,
 'rs': 12}

At first I thought about an authorisation error because the function was not in de name list (we choose to authorize only the functions which are necessary), but after adding the function to the namelist in zvm, it still gave the same error.

We see the call coming to zvm (an example):
00025 2019-01-09 12:52:15 REQUE DMSRSRQN REQ_ACC VSMREQIU AF_IUCV CLDCONO1
00026 2019-01-09 12:52:15 ENTRY DMSRSRQT REQ_IUCV VSMREQIU
00027 2019-01-09 12:52:15 ENTRY DMSWSWRK CALLDIRM VSMWORK1 on VSMWORK1 req(23294719) for(EMP) SYSTEM_RDR_FILE_MANAGE
00028 2019-01-09 12:52:15 REQUE DMSRSRQT REQ_IUCV VSMREQIU CLDCONO1 SYSTEM_RDR_FILE_MANAGE 23294719
00029 2019-01-09 12:52:15 ENTRY DMSWSSMP Work_SMP VSMWORK1 SYSTEM_RDR_FILE_MANAGE CLDCONO1 EMP 13 spoolids=all"
00030 2019-01-09 12:52:15 ENTRY DMSSIPTS Work_PTS VSMWORK1 SYSTEM_RDR_FILE_MANAGE EMP 13 spoolids=all"

The strangest is the " at the end of the command (after all). With a hex editor this is a 00 token.

So maybe a translation error between smcli and the smapi.

Environment: z/VM 6.4 build 1801
Suse 12.3 Linux guest and Cloud Connector
CLDCONO1 is the cloud connector linux working on ip 10.35.4.60
Emp is the new linux guest

[jichenjc (jichenjc)]

Bill, can you take a look?

[Huang Rui (bjhuangr)]

Does your z/VM with APAR VM66120 applied?

[Herald ten Dam (damsteen)]

I think you hit the nail, we missed this one, we thought it was in 640 already. We will now apply FIX 1802 for z/VM 6.4.

It looks a bit strange to me that I want to deploy an image on a client and it calls a function I don't have deployed on the system.

Thanks

[cao biao (flytiger)]

Just as Huang Rui said and we also mentioned in the Pre-requirement of docs(https://cloudlib4zvm.readthedocs.io/en/latest/quickstart.html) that VM66120 is required.
Apply it and if there still a problem pls tell us, thanks.

[Herald ten Dam (damsteen)]

For the 1st install I used 1.3 documentation. In that it is not mentioned, now it is mentioned. We will install it and see what happens.
Thanks

[jichenjc (jichenjc)]

you are right, 1.3 doesn't have the info (we found the info is needed but didn't backport)
@Bill, can you help to backport the doc patch to 1.3 branch