diff --git a/__tests__/__integration__/cli/view/job-status-by-jobid/__snapshots__/cli.view.job-status-by-jobid.test.ts.snap b/__tests__/__integration__/cli/view/job-status-by-jobid/__snapshots__/cli.view.job-status-by-jobid.test.ts.snap index b2c22b93..46e9a99c 100644 --- a/__tests__/__integration__/cli/view/job-status-by-jobid/__snapshots__/cli.view.job-status-by-jobid.test.ts.snap +++ b/__tests__/__integration__/cli/view/job-status-by-jobid/__snapshots__/cli.view.job-status-by-jobid.test.ts.snap @@ -17,12 +17,12 @@ exports[`view job-status-by-jobid command should display view job status by job USAGE ----- - zowe zos-ftp view job-status-by-jobid [options] + zowe zos-ftp view job-status-by-jobid [options] POSITIONAL ARGUMENTS -------------------- - jobid (string) + jobId (string) The ID of the jobfor which you would like to list spool files @@ -178,8 +178,8 @@ exports[`view job-status-by-jobid command should display view job status by job \\"success\\": true, \\"exitCode\\": 0, \\"message\\": \\"The help was constructed for command: job-status-by-jobid.\\", - \\"stdout\\": \\"\\\\n COMMAND NAME\\\\n ------------\\\\n\\\\n job-status-by-jobid | jsbj\\\\n\\\\n DESCRIPTION\\\\n -----------\\\\n\\\\n View status details of a single z/OS job on spool/JES queues. The command does\\\\n not prevalidate the JOBID.\\\\n\\\\n USAGE\\\\n -----\\\\n\\\\n zowe zos-ftp view job-status-by-jobid [options]\\\\n\\\\n POSITIONAL ARGUMENTS\\\\n --------------------\\\\n\\\\n jobid\\\\t\\\\t (string)\\\\n\\\\n The ID of the jobfor which you would like to list spool files\\\\n\\\\n FTP CONNECTION OPTIONS\\\\n ----------------------\\\\n\\\\n --host | -H (string)\\\\n\\\\n The hostname or IP address of the z/OS server to connect to.\\\\n\\\\n --port | -P (number)\\\\n\\\\n The port of the z/OS FTP server.\\\\n\\\\n Default value: 21\\\\n\\\\n --user | -u (string)\\\\n\\\\n Username for authentication on z/OS\\\\n\\\\n --password | -p | --pass | --pw (string)\\\\n\\\\n Password to authenticate to FTP.\\\\n\\\\n --secure-ftp (boolean)\\\\n\\\\n Set to true for both control and data connection encryption, 'control' for\\\\n control connection encryption only, or 'implicit' for implicitly encrypted\\\\n control connection (this mode is deprecated in modern times, but usually uses\\\\n port 990). Note: Unfortunately, this plugin's functionality only works with FTP\\\\n and FTPS, not 'SFTP' which is FTP over SSH.\\\\n\\\\n Default value: true\\\\n\\\\n --connection-timeout | --ct (number)\\\\n\\\\n How long (in milliseconds) to wait for the control connection to be established.\\\\n\\\\n Default value: 10000\\\\n\\\\n TLS / SECURE CONNECTION OPTIONS\\\\n -------------------------------\\\\n\\\\n --reject-unauthorized | --ru (boolean)\\\\n\\\\n Reject self-signed certificates. Only specify this if you are connecting to a\\\\n secure FTP instance.\\\\n\\\\n --server-name | --sn (string)\\\\n\\\\n Server name for the SNI (Server Name Indication) TLS extension. Only specify if\\\\n you are connecting securely\\\\n\\\\n PROFILE OPTIONS\\\\n ---------------\\\\n\\\\n --zftp-profile | --zftp-p (string)\\\\n\\\\n The name of a (zftp) profile to load for this command execution.\\\\n\\\\n --base-profile | --base-p (string)\\\\n\\\\n The name of a (base) profile to load for this command execution.\\\\n\\\\n BASE CONNECTION OPTIONS\\\\n -----------------------\\\\n\\\\n --token-type | --tt (string)\\\\n\\\\n The type of token to get and use for the API. Omit this option to use the\\\\n default token type, which is provided by 'zowe auth login'.\\\\n\\\\n --token-value | --tv (string)\\\\n\\\\n The value of the token to pass to the API.\\\\n\\\\n --cert-file (local file path)\\\\n\\\\n The file path to a certificate file to use for authentication.\\\\n\\\\n Note: The CLI does not support certificate files that require a password. For\\\\n more information, search Troubleshooting PEM Certificates in Zowe Docs.\\\\n\\\\n --cert-key-file (local file path)\\\\n\\\\n The file path to a certificate key file to use for authentication\\\\n\\\\n RESPONSE FORMAT OPTIONS\\\\n -----------------------\\\\n\\\\n --response-format-filter | --rff (array)\\\\n\\\\n Filter (include) fields in the response. Accepts an array of field/property\\\\n names to include in the output response. You can filter JSON objects properties\\\\n OR table columns/fields. In addition, you can use this option in conjunction\\\\n with '--response-format-type' to reduce the output of a command to a single\\\\n field/property or a list of a single field/property.\\\\n\\\\n --response-format-type | --rft (string)\\\\n\\\\n The command response output format type. Must be one of the following:\\\\n\\\\n table: Formats output data as a table. Use this option when the output data is\\\\n an array of homogeneous JSON objects. Each property of the object will become a\\\\n column in the table.\\\\n\\\\n list: Formats output data as a list of strings. Can be used on any data type\\\\n (JSON objects/arrays) are stringified and a new line is added after each entry\\\\n in an array.\\\\n\\\\n object: Formats output data as a list of prettified objects (or single object).\\\\n Can be used in place of \\\\\\"table\\\\\\" to change from tabular output to a list of\\\\n prettified objects.\\\\n\\\\n string: Formats output data as a string. JSON objects/arrays are stringified.\\\\n\\\\n Allowed values: table, list, object, string\\\\n\\\\n --response-format-header | --rfh (boolean)\\\\n\\\\n If \\\\\\"--response-format-type table\\\\\\" is specified, include the column headers in\\\\n the output.\\\\n\\\\n GLOBAL OPTIONS\\\\n --------------\\\\n\\\\n --show-inputs-only (boolean)\\\\n\\\\n Show command inputs and do not run the command\\\\n\\\\n --response-format-json | --rfj (boolean)\\\\n\\\\n Produce JSON formatted data from a command\\\\n\\\\n --help | -h (boolean)\\\\n\\\\n Display help text\\\\n\\\\n --help-web | --hw (boolean)\\\\n\\\\n Display HTML help in browser\\\\n\\\\n EXAMPLES\\\\n --------\\\\n\\\\n - View the status for the job with ID \\\\\\"JOB00123\\\\\\" (optionally\\\\n abbreviating the ID):\\\\n\\\\n $ zowe zos-ftp view job-status-by-jobid j123\\\\n\\\\n\\", + \\"stdout\\": \\"\\\\n COMMAND NAME\\\\n ------------\\\\n\\\\n job-status-by-jobid | jsbj\\\\n\\\\n DESCRIPTION\\\\n -----------\\\\n\\\\n View status details of a single z/OS job on spool/JES queues. The command does\\\\n not prevalidate the JOBID.\\\\n\\\\n USAGE\\\\n -----\\\\n\\\\n zowe zos-ftp view job-status-by-jobid [options]\\\\n\\\\n POSITIONAL ARGUMENTS\\\\n --------------------\\\\n\\\\n jobId\\\\t\\\\t (string)\\\\n\\\\n The ID of the jobfor which you would like to list spool files\\\\n\\\\n FTP CONNECTION OPTIONS\\\\n ----------------------\\\\n\\\\n --host | -H (string)\\\\n\\\\n The hostname or IP address of the z/OS server to connect to.\\\\n\\\\n --port | -P (number)\\\\n\\\\n The port of the z/OS FTP server.\\\\n\\\\n Default value: 21\\\\n\\\\n --user | -u (string)\\\\n\\\\n Username for authentication on z/OS\\\\n\\\\n --password | -p | --pass | --pw (string)\\\\n\\\\n Password to authenticate to FTP.\\\\n\\\\n --secure-ftp (boolean)\\\\n\\\\n Set to true for both control and data connection encryption, 'control' for\\\\n control connection encryption only, or 'implicit' for implicitly encrypted\\\\n control connection (this mode is deprecated in modern times, but usually uses\\\\n port 990). Note: Unfortunately, this plugin's functionality only works with FTP\\\\n and FTPS, not 'SFTP' which is FTP over SSH.\\\\n\\\\n Default value: true\\\\n\\\\n --connection-timeout | --ct (number)\\\\n\\\\n How long (in milliseconds) to wait for the control connection to be established.\\\\n\\\\n Default value: 10000\\\\n\\\\n TLS / SECURE CONNECTION OPTIONS\\\\n -------------------------------\\\\n\\\\n --reject-unauthorized | --ru (boolean)\\\\n\\\\n Reject self-signed certificates. Only specify this if you are connecting to a\\\\n secure FTP instance.\\\\n\\\\n --server-name | --sn (string)\\\\n\\\\n Server name for the SNI (Server Name Indication) TLS extension. Only specify if\\\\n you are connecting securely\\\\n\\\\n PROFILE OPTIONS\\\\n ---------------\\\\n\\\\n --zftp-profile | --zftp-p (string)\\\\n\\\\n The name of a (zftp) profile to load for this command execution.\\\\n\\\\n --base-profile | --base-p (string)\\\\n\\\\n The name of a (base) profile to load for this command execution.\\\\n\\\\n BASE CONNECTION OPTIONS\\\\n -----------------------\\\\n\\\\n --token-type | --tt (string)\\\\n\\\\n The type of token to get and use for the API. Omit this option to use the\\\\n default token type, which is provided by 'zowe auth login'.\\\\n\\\\n --token-value | --tv (string)\\\\n\\\\n The value of the token to pass to the API.\\\\n\\\\n --cert-file (local file path)\\\\n\\\\n The file path to a certificate file to use for authentication.\\\\n\\\\n Note: The CLI does not support certificate files that require a password. For\\\\n more information, search Troubleshooting PEM Certificates in Zowe Docs.\\\\n\\\\n --cert-key-file (local file path)\\\\n\\\\n The file path to a certificate key file to use for authentication\\\\n\\\\n RESPONSE FORMAT OPTIONS\\\\n -----------------------\\\\n\\\\n --response-format-filter | --rff (array)\\\\n\\\\n Filter (include) fields in the response. Accepts an array of field/property\\\\n names to include in the output response. You can filter JSON objects properties\\\\n OR table columns/fields. In addition, you can use this option in conjunction\\\\n with '--response-format-type' to reduce the output of a command to a single\\\\n field/property or a list of a single field/property.\\\\n\\\\n --response-format-type | --rft (string)\\\\n\\\\n The command response output format type. Must be one of the following:\\\\n\\\\n table: Formats output data as a table. Use this option when the output data is\\\\n an array of homogeneous JSON objects. Each property of the object will become a\\\\n column in the table.\\\\n\\\\n list: Formats output data as a list of strings. Can be used on any data type\\\\n (JSON objects/arrays) are stringified and a new line is added after each entry\\\\n in an array.\\\\n\\\\n object: Formats output data as a list of prettified objects (or single object).\\\\n Can be used in place of \\\\\\"table\\\\\\" to change from tabular output to a list of\\\\n prettified objects.\\\\n\\\\n string: Formats output data as a string. JSON objects/arrays are stringified.\\\\n\\\\n Allowed values: table, list, object, string\\\\n\\\\n --response-format-header | --rfh (boolean)\\\\n\\\\n If \\\\\\"--response-format-type table\\\\\\" is specified, include the column headers in\\\\n the output.\\\\n\\\\n GLOBAL OPTIONS\\\\n --------------\\\\n\\\\n --show-inputs-only (boolean)\\\\n\\\\n Show command inputs and do not run the command\\\\n\\\\n --response-format-json | --rfj (boolean)\\\\n\\\\n Produce JSON formatted data from a command\\\\n\\\\n --help | -h (boolean)\\\\n\\\\n Display help text\\\\n\\\\n --help-web | --hw (boolean)\\\\n\\\\n Display HTML help in browser\\\\n\\\\n EXAMPLES\\\\n --------\\\\n\\\\n - View the status for the job with ID \\\\\\"JOB00123\\\\\\" (optionally\\\\n abbreviating the ID):\\\\n\\\\n $ zowe zos-ftp view job-status-by-jobid j123\\\\n\\\\n\\", \\"stderr\\": \\"\\", - \\"data\\": \\"\\\\n COMMAND NAME\\\\n ------------\\\\n\\\\n job-status-by-jobid | jsbj\\\\n\\\\n DESCRIPTION\\\\n -----------\\\\n\\\\n View status details of a single z/OS job on spool/JES queues. The command does\\\\n not prevalidate the JOBID.\\\\n\\\\n USAGE\\\\n -----\\\\n\\\\n zowe zos-ftp view job-status-by-jobid [options]\\\\n\\\\n POSITIONAL ARGUMENTS\\\\n --------------------\\\\n\\\\n jobid\\\\t\\\\t (string)\\\\n\\\\n The ID of the jobfor which you would like to list spool files\\\\n\\\\n FTP CONNECTION OPTIONS\\\\n ----------------------\\\\n\\\\n --host | -H (string)\\\\n\\\\n The hostname or IP address of the z/OS server to connect to.\\\\n\\\\n --port | -P (number)\\\\n\\\\n The port of the z/OS FTP server.\\\\n\\\\n Default value: 21\\\\n\\\\n --user | -u (string)\\\\n\\\\n Username for authentication on z/OS\\\\n\\\\n --password | -p | --pass | --pw (string)\\\\n\\\\n Password to authenticate to FTP.\\\\n\\\\n --secure-ftp (boolean)\\\\n\\\\n Set to true for both control and data connection encryption, 'control' for\\\\n control connection encryption only, or 'implicit' for implicitly encrypted\\\\n control connection (this mode is deprecated in modern times, but usually uses\\\\n port 990). Note: Unfortunately, this plugin's functionality only works with FTP\\\\n and FTPS, not 'SFTP' which is FTP over SSH.\\\\n\\\\n Default value: true\\\\n\\\\n --connection-timeout | --ct (number)\\\\n\\\\n How long (in milliseconds) to wait for the control connection to be established.\\\\n\\\\n Default value: 10000\\\\n\\\\n TLS / SECURE CONNECTION OPTIONS\\\\n -------------------------------\\\\n\\\\n --reject-unauthorized | --ru (boolean)\\\\n\\\\n Reject self-signed certificates. Only specify this if you are connecting to a\\\\n secure FTP instance.\\\\n\\\\n --server-name | --sn (string)\\\\n\\\\n Server name for the SNI (Server Name Indication) TLS extension. Only specify if\\\\n you are connecting securely\\\\n\\\\n PROFILE OPTIONS\\\\n ---------------\\\\n\\\\n --zftp-profile | --zftp-p (string)\\\\n\\\\n The name of a (zftp) profile to load for this command execution.\\\\n\\\\n --base-profile | --base-p (string)\\\\n\\\\n The name of a (base) profile to load for this command execution.\\\\n\\\\n BASE CONNECTION OPTIONS\\\\n -----------------------\\\\n\\\\n --token-type | --tt (string)\\\\n\\\\n The type of token to get and use for the API. Omit this option to use the\\\\n default token type, which is provided by 'zowe auth login'.\\\\n\\\\n --token-value | --tv (string)\\\\n\\\\n The value of the token to pass to the API.\\\\n\\\\n --cert-file (local file path)\\\\n\\\\n The file path to a certificate file to use for authentication.\\\\n\\\\n Note: The CLI does not support certificate files that require a password. For\\\\n more information, search Troubleshooting PEM Certificates in Zowe Docs.\\\\n\\\\n --cert-key-file (local file path)\\\\n\\\\n The file path to a certificate key file to use for authentication\\\\n\\\\n RESPONSE FORMAT OPTIONS\\\\n -----------------------\\\\n\\\\n --response-format-filter | --rff (array)\\\\n\\\\n Filter (include) fields in the response. Accepts an array of field/property\\\\n names to include in the output response. You can filter JSON objects properties\\\\n OR table columns/fields. In addition, you can use this option in conjunction\\\\n with '--response-format-type' to reduce the output of a command to a single\\\\n field/property or a list of a single field/property.\\\\n\\\\n --response-format-type | --rft (string)\\\\n\\\\n The command response output format type. Must be one of the following:\\\\n\\\\n table: Formats output data as a table. Use this option when the output data is\\\\n an array of homogeneous JSON objects. Each property of the object will become a\\\\n column in the table.\\\\n\\\\n list: Formats output data as a list of strings. Can be used on any data type\\\\n (JSON objects/arrays) are stringified and a new line is added after each entry\\\\n in an array.\\\\n\\\\n object: Formats output data as a list of prettified objects (or single object).\\\\n Can be used in place of \\\\\\"table\\\\\\" to change from tabular output to a list of\\\\n prettified objects.\\\\n\\\\n string: Formats output data as a string. JSON objects/arrays are stringified.\\\\n\\\\n Allowed values: table, list, object, string\\\\n\\\\n --response-format-header | --rfh (boolean)\\\\n\\\\n If \\\\\\"--response-format-type table\\\\\\" is specified, include the column headers in\\\\n the output.\\\\n\\\\n GLOBAL OPTIONS\\\\n --------------\\\\n\\\\n --show-inputs-only (boolean)\\\\n\\\\n Show command inputs and do not run the command\\\\n\\\\n --response-format-json | --rfj (boolean)\\\\n\\\\n Produce JSON formatted data from a command\\\\n\\\\n --help | -h (boolean)\\\\n\\\\n Display help text\\\\n\\\\n --help-web | --hw (boolean)\\\\n\\\\n Display HTML help in browser\\\\n\\\\n EXAMPLES\\\\n --------\\\\n\\\\n - View the status for the job with ID \\\\\\"JOB00123\\\\\\" (optionally\\\\n abbreviating the ID):\\\\n\\\\n $ zowe zos-ftp view job-status-by-jobid j123\\\\n\\\\n\\" + \\"data\\": \\"\\\\n COMMAND NAME\\\\n ------------\\\\n\\\\n job-status-by-jobid | jsbj\\\\n\\\\n DESCRIPTION\\\\n -----------\\\\n\\\\n View status details of a single z/OS job on spool/JES queues. The command does\\\\n not prevalidate the JOBID.\\\\n\\\\n USAGE\\\\n -----\\\\n\\\\n zowe zos-ftp view job-status-by-jobid [options]\\\\n\\\\n POSITIONAL ARGUMENTS\\\\n --------------------\\\\n\\\\n jobId\\\\t\\\\t (string)\\\\n\\\\n The ID of the jobfor which you would like to list spool files\\\\n\\\\n FTP CONNECTION OPTIONS\\\\n ----------------------\\\\n\\\\n --host | -H (string)\\\\n\\\\n The hostname or IP address of the z/OS server to connect to.\\\\n\\\\n --port | -P (number)\\\\n\\\\n The port of the z/OS FTP server.\\\\n\\\\n Default value: 21\\\\n\\\\n --user | -u (string)\\\\n\\\\n Username for authentication on z/OS\\\\n\\\\n --password | -p | --pass | --pw (string)\\\\n\\\\n Password to authenticate to FTP.\\\\n\\\\n --secure-ftp (boolean)\\\\n\\\\n Set to true for both control and data connection encryption, 'control' for\\\\n control connection encryption only, or 'implicit' for implicitly encrypted\\\\n control connection (this mode is deprecated in modern times, but usually uses\\\\n port 990). Note: Unfortunately, this plugin's functionality only works with FTP\\\\n and FTPS, not 'SFTP' which is FTP over SSH.\\\\n\\\\n Default value: true\\\\n\\\\n --connection-timeout | --ct (number)\\\\n\\\\n How long (in milliseconds) to wait for the control connection to be established.\\\\n\\\\n Default value: 10000\\\\n\\\\n TLS / SECURE CONNECTION OPTIONS\\\\n -------------------------------\\\\n\\\\n --reject-unauthorized | --ru (boolean)\\\\n\\\\n Reject self-signed certificates. Only specify this if you are connecting to a\\\\n secure FTP instance.\\\\n\\\\n --server-name | --sn (string)\\\\n\\\\n Server name for the SNI (Server Name Indication) TLS extension. Only specify if\\\\n you are connecting securely\\\\n\\\\n PROFILE OPTIONS\\\\n ---------------\\\\n\\\\n --zftp-profile | --zftp-p (string)\\\\n\\\\n The name of a (zftp) profile to load for this command execution.\\\\n\\\\n --base-profile | --base-p (string)\\\\n\\\\n The name of a (base) profile to load for this command execution.\\\\n\\\\n BASE CONNECTION OPTIONS\\\\n -----------------------\\\\n\\\\n --token-type | --tt (string)\\\\n\\\\n The type of token to get and use for the API. Omit this option to use the\\\\n default token type, which is provided by 'zowe auth login'.\\\\n\\\\n --token-value | --tv (string)\\\\n\\\\n The value of the token to pass to the API.\\\\n\\\\n --cert-file (local file path)\\\\n\\\\n The file path to a certificate file to use for authentication.\\\\n\\\\n Note: The CLI does not support certificate files that require a password. For\\\\n more information, search Troubleshooting PEM Certificates in Zowe Docs.\\\\n\\\\n --cert-key-file (local file path)\\\\n\\\\n The file path to a certificate key file to use for authentication\\\\n\\\\n RESPONSE FORMAT OPTIONS\\\\n -----------------------\\\\n\\\\n --response-format-filter | --rff (array)\\\\n\\\\n Filter (include) fields in the response. Accepts an array of field/property\\\\n names to include in the output response. You can filter JSON objects properties\\\\n OR table columns/fields. In addition, you can use this option in conjunction\\\\n with '--response-format-type' to reduce the output of a command to a single\\\\n field/property or a list of a single field/property.\\\\n\\\\n --response-format-type | --rft (string)\\\\n\\\\n The command response output format type. Must be one of the following:\\\\n\\\\n table: Formats output data as a table. Use this option when the output data is\\\\n an array of homogeneous JSON objects. Each property of the object will become a\\\\n column in the table.\\\\n\\\\n list: Formats output data as a list of strings. Can be used on any data type\\\\n (JSON objects/arrays) are stringified and a new line is added after each entry\\\\n in an array.\\\\n\\\\n object: Formats output data as a list of prettified objects (or single object).\\\\n Can be used in place of \\\\\\"table\\\\\\" to change from tabular output to a list of\\\\n prettified objects.\\\\n\\\\n string: Formats output data as a string. JSON objects/arrays are stringified.\\\\n\\\\n Allowed values: table, list, object, string\\\\n\\\\n --response-format-header | --rfh (boolean)\\\\n\\\\n If \\\\\\"--response-format-type table\\\\\\" is specified, include the column headers in\\\\n the output.\\\\n\\\\n GLOBAL OPTIONS\\\\n --------------\\\\n\\\\n --show-inputs-only (boolean)\\\\n\\\\n Show command inputs and do not run the command\\\\n\\\\n --response-format-json | --rfj (boolean)\\\\n\\\\n Produce JSON formatted data from a command\\\\n\\\\n --help | -h (boolean)\\\\n\\\\n Display help text\\\\n\\\\n --help-web | --hw (boolean)\\\\n\\\\n Display HTML help in browser\\\\n\\\\n EXAMPLES\\\\n --------\\\\n\\\\n - View the status for the job with ID \\\\\\"JOB00123\\\\\\" (optionally\\\\n abbreviating the ID):\\\\n\\\\n $ zowe zos-ftp view job-status-by-jobid j123\\\\n\\\\n\\" }" `; diff --git a/__tests__/__unit__/cli/delete/uss-file/UssFile.Handler.test.ts b/__tests__/__unit__/cli/delete/uss-file/UssFile.Handler.test.ts index c51a25c8..394f0e8f 100644 --- a/__tests__/__unit__/cli/delete/uss-file/UssFile.Handler.test.ts +++ b/__tests__/__unit__/cli/delete/uss-file/UssFile.Handler.test.ts @@ -23,7 +23,7 @@ describe("Delete uss file handler", () => { ussFile: "ussFile1" }, connection: { - deleteDataset: jest.fn().mockReturnValue(Promise.resolve("")) + deleteFile: jest.fn().mockReturnValue(Promise.resolve("")) }, response: mockResponse }; diff --git a/__tests__/__unit__/cli/list/data-set/__snapshots__/DataSet.Handler.test.ts.snap b/__tests__/__unit__/cli/list/data-set/__snapshots__/DataSet.Handler.test.ts.snap index 1397c604..e92b944d 100644 --- a/__tests__/__unit__/cli/list/data-set/__snapshots__/DataSet.Handler.test.ts.snap +++ b/__tests__/__unit__/cli/list/data-set/__snapshots__/DataSet.Handler.test.ts.snap @@ -14,7 +14,7 @@ Array [ exports[`List data set handler should return correct message if the data set is found. 2`] = ` Object { "fields": Array [ - "dsname", + "name", ], "format": "table", "output": Array [ @@ -33,7 +33,7 @@ exports[`List data set handler should return no data set if the data set is not exports[`List data set handler should return no data set if the data set is not found. 2`] = ` Object { "fields": Array [ - "dsname", + "name", ], "format": "table", "output": Array [], diff --git a/__tests__/__unit__/cli/list/spool-files-by-jobid/__snapshots__/SpoolFilesByJobid.Handler.test.ts.snap b/__tests__/__unit__/cli/list/spool-files-by-jobid/__snapshots__/SpoolFilesByJobid.Handler.test.ts.snap index f9f99c54..52bf413c 100644 --- a/__tests__/__unit__/cli/list/spool-files-by-jobid/__snapshots__/SpoolFilesByJobid.Handler.test.ts.snap +++ b/__tests__/__unit__/cli/list/spool-files-by-jobid/__snapshots__/SpoolFilesByJobid.Handler.test.ts.snap @@ -4,9 +4,9 @@ exports[`List spool files by job id handler should return correct message if at Object { "fields": Array [ "id", - "ddname", - "procstep", - "stepname", + "ddName", + "procStep", + "stepName", ], "format": "table", "output": Array [ @@ -35,9 +35,9 @@ exports[`List spool files by job id handler should return correct message if at Object { "fields": Array [ "id", - "ddname", - "procstep", - "stepname", + "ddName", + "procStep", + "stepName", ], "format": "table", "output": Array [ @@ -57,9 +57,9 @@ exports[`List spool files by job id handler should return no spool file if the n Object { "fields": Array [ "id", - "ddname", - "procstep", - "stepname", + "ddName", + "procStep", + "stepName", ], "format": "table", "output": Array [], diff --git a/__tests__/__unit__/cli/upload/file-to-uss-file/FileToUssFile.Handler.test.ts b/__tests__/__unit__/cli/upload/file-to-uss-file/FileToUssFile.Handler.test.ts index e745c75a..79c06721 100644 --- a/__tests__/__unit__/cli/upload/file-to-uss-file/FileToUssFile.Handler.test.ts +++ b/__tests__/__unit__/cli/upload/file-to-uss-file/FileToUssFile.Handler.test.ts @@ -29,7 +29,7 @@ describe("Upload file to data set handler", () => { ussFile: "/u/user/ussfile1" }, connection: { - uploadDataset: jest.fn().mockReturnValue(Promise.resolve("")) + uploadFile: jest.fn().mockReturnValue(Promise.resolve("")) }, response: mockResponse }; diff --git a/__tests__/__unit__/cli/upload/stdin-to-uss-file/StdinToUssFile.Handler.test.ts b/__tests__/__unit__/cli/upload/stdin-to-uss-file/StdinToUssFile.Handler.test.ts index f45fd362..fdb2bcee 100644 --- a/__tests__/__unit__/cli/upload/stdin-to-uss-file/StdinToUssFile.Handler.test.ts +++ b/__tests__/__unit__/cli/upload/stdin-to-uss-file/StdinToUssFile.Handler.test.ts @@ -27,7 +27,7 @@ describe("Upload stdin to USS file handler", () => { ussFile: "/u/user/ussfile1" }, connection: { - uploadDataset: jest.fn().mockReturnValue(Promise.resolve("")) + uploadFile: jest.fn().mockReturnValue(Promise.resolve("")) }, response: mockResponse }; diff --git a/__tests__/__unit__/cli/view/__snapshots__/View.definition.test.ts.snap b/__tests__/__unit__/cli/view/__snapshots__/View.definition.test.ts.snap index b6257a59..b519ef26 100644 --- a/__tests__/__unit__/cli/view/__snapshots__/View.definition.test.ts.snap +++ b/__tests__/__unit__/cli/view/__snapshots__/View.definition.test.ts.snap @@ -111,7 +111,7 @@ Object { "positionals": Array [ Object { "description": "The ID of the jobfor which you would like to list spool files", - "name": "jobid", + "name": "jobId", "required": true, "type": "string", }, diff --git a/__tests__/__unit__/cli/view/job-status-by-jobid/JobStatusByJobId.Handler.test.ts b/__tests__/__unit__/cli/view/job-status-by-jobid/JobStatusByJobId.Handler.test.ts index 7d4aede0..f0ead71f 100644 --- a/__tests__/__unit__/cli/view/job-status-by-jobid/JobStatusByJobId.Handler.test.ts +++ b/__tests__/__unit__/cli/view/job-status-by-jobid/JobStatusByJobId.Handler.test.ts @@ -18,8 +18,8 @@ describe("View job status by jobid handler", () => { const handler = new ViewJobStatusByJobIdHandler(); const jobDetails = { - jobname: "jobname1", - jobid: "jobid1", + jobName: "jobName1", + jobId: "jobId1", owner: "owner1", status: "success", rc: 0 @@ -28,7 +28,7 @@ describe("View job status by jobid handler", () => { const mockResponse = TestUtils.getMockResponse(); const mockParams: any = { arguments: { - jobid: "jobID1" + jobId: "jobID1" }, connection: { getJobStatus: jest.fn().mockReturnValue(Promise.resolve(jobDetails)) diff --git a/__tests__/__unit__/cli/view/job-status-by-jobid/__snapshots__/JobStatusByJobId.Handler.test.ts.snap b/__tests__/__unit__/cli/view/job-status-by-jobid/__snapshots__/JobStatusByJobId.Handler.test.ts.snap index 1941a8d9..3d69551a 100644 --- a/__tests__/__unit__/cli/view/job-status-by-jobid/__snapshots__/JobStatusByJobId.Handler.test.ts.snap +++ b/__tests__/__unit__/cli/view/job-status-by-jobid/__snapshots__/JobStatusByJobId.Handler.test.ts.snap @@ -2,8 +2,8 @@ exports[`View job status by jobid handler should return correct job status if the job is found. 1`] = ` Object { - "jobid": "jobid1", - "jobname": "jobname1", + "jobId": "jobId1", + "jobName": "jobName1", "owner": "owner1", "rc": 0, "status": "success", @@ -13,8 +13,8 @@ Object { exports[`View job status by jobid handler should return correct job status if the job is found. 2`] = ` Object { "fields": Array [ - "jobname", - "jobid", + "jobName", + "jobId", "owner", "status", "rc", @@ -22,8 +22,8 @@ Object { ], "format": "object", "output": Object { - "jobid": "jobid1", - "jobname": "jobname1", + "jobId": "jobId1", + "jobName": "jobName1", "owner": "owner1", "rc": 0, "status": "success",