Skip to content

Conversation

@LShort-DM
Copy link
Collaborator

I added comments to the file. You cant see the comments in Preview. You must look at the Code.

Copy link
Member

@johnmckeever johnmckeever left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the comments, @LShort-DM.

1. Under Personal credentials > Input method select **Enter credentials manually**.
1. Check the **Use my platform login credentials** then click **Test connection**.
1. Assuming you have a successful connection, click **Save**.
<!-- if the connection is NOT successfull, what is fhe most likely issue -->
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've added (in the next commit) a link to the CP4D documentation 'Adding connections to data sources in a project' which goes into detail about this process. If IBM want troubleshooting steps, then they should be linked from that page.

1. For **Test data connection type** select **Storage Volume**.
1. For **Test data storage** select the name of the Storage volume you created in the step above.
1. For **Default DataStage Test case job suffix** specify a suffix which will be appended to all test case jobs to help distinguish them in the job log from invocations of their associated flows. e.g. ` DataStage TestCase Job`. Note the leading space included here, as DataStage will not automatically add one for you.
<!-- Does this mean the actual text ' Datastage TestCase Job' will be appended to all test case jobs? -->
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. I think I'm already fairly clear on that question ...

... a suffix which will be appended to all test case jobs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants