--show-inputs-only not working for zos-files copy data-set-cross-lpar

[drb1972]

--show-inputs-only not showing values for zowe zos-files copy data-set-cross-lpar CLI command but executing the command directly (succesfully copied).

Expected: Display commandValues

Actual results:
PS C:\zowe>zowe zos-files copy data-set-cross-lpar PROD001.lib.del PROD001.lib.del.copy --target-zosmf-profile b043.zosmf --zosmf-profile r133.zosmf --show-inputs-only
Data set copied successfully.

CLI Version: 8.12.0
Zowe Release Version: v3.1.0
@broadcom/[email protected]
@broadcom/[email protected]
@broadcom/[email protected]
@broadcom/[email protected]
@broadcom/[email protected]
@broadcom/[email protected]
@microfocus/[email protected]
@zowe/[email protected]
@zowe/[email protected]
@zowe/[email protected]
@zowe/[email protected]
node: v20.18.0
npm: 9.2.0
ZOWE_SHOW_SECURE_ARGS = true
Windows 10 Pro 22H2
O.S. platform: win32
O.S. architecture: x64
powershell
Daemon mode disabled

[github-actions]

Thank you for creating a bug report.
We will investigate the bug and evaluate its impact on the product.
If you haven't already, please ensure you have provided steps to reproduce the bug and as much context as possible.

[awharn]

It appears showInputsOnly is not checked for commands using chained handlers, and only done for commands with a single handler.

For single handlers, the logic is here:

zowe-cli/packages/imperative/src/cmd/src/CommandProcessor.ts

Lines 615 to 621 in b91b989

	try {
	if (handlerParms.arguments.showInputsOnly) {
	this.showInputsOnly(response, handlerParms);
	} else {
	await handler.process(handlerParms);
	}
	} catch (processErr) {

For chained handlers, we would want to replicate the same behavior here:

zowe-cli/packages/imperative/src/cmd/src/CommandProcessor.ts

Lines 671 to 694 in b91b989

	try {
	await handler.process({
	response: chainedResponse,
	arguments: ChainedHandlerService.getArguments(
	this.mCommandRootName,
	this.definition.chainedHandlers,
	chainedHandlerIndex,
	chainedResponses,
	preparedArgs,
	this.log
	),
	positionals: preparedArgs._,
	definition: this.definition,
	fullDefinition: this.fullDefinition,
	stdin: this.getStdinStream(),
	isChained: true
	});
	const builtResponse = chainedResponse.buildJsonResponse();
	chainedResponses.push(builtResponse.data);
	// save the stdout and stderr to pass to the next chained handler (if any)
	bufferedStdOut = builtResponse.stdout;
	bufferedStdErr = builtResponse.stderr;
	} catch (processErr) {