You can always post in the Github Discussion
https://github.com/orgs/codefori/discussions
or on Zulip https://chat.ibmioss.org/

1. It prompts with the command when you compile and you can change the
library there. If your action has a ? in front of it, it gives you a chance
to change it. I think there is also a way to set a custom variable in the
latest version 3.0+ in the Environment View. I haven't tried it yet. Can't
send a screenshot thus the reason for Zulip.

2. When I right click on source member and click copy and tell it where to
copy, it copies the description along with it, so not sure how you are
copying?

3. I'm no help as I haven't gotten Debug set up.

message: 1
date: Fri, 29 May 2026 13:48:21 +0000
from: Greg Wilburn <gwilburn@xxxxxxxxxxxxxxxxxxxxxxx>
subject: VS Code Questions

I've been trying to use VS Code and get it setup for our environment.
There are a few things I can't seem to clear up.


1. Often, my source and program objects are not in the same libraries.
I've created custom actions for compiling - but it sure would be nice if I
could create a SINGLE action that would prompt for the program object
library. I fooled round with suggestions from Google AI to no avail.
2. I often copy a source member for testing. While I am able to copy,
it doesn't include the source member description.
Is there a way around this?
3. Debugging: Setting a SEP fails with many of my source members, but
not all. Error is:
"Failed to determine object type. Ensure the object exists and is a
program (*PGM) or service program (*SRVPGM)."

** This occurs even if the library where the pgm object exists is set as
CURLIB **

Is there a better place to ask these questions? Google seems to be nearly
clueless as most answers are incorrect.

TIA,
Greg




As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.