Description
Describe the bug
Creating a data step seems to be hard for the copilot. It'll mostly try to solve the problem using a proc sql or some other procedure, even though you specifically instruct it to use a datastep.
*3 Examples of code generations, where only the last one is correct **
/ use a datastep to load the class dataset from the sashelp library and write it to the casuser caslib */
proc import datafile="/bigdisk/lax/frvere/gai-codesas-data/sample_datasets/references/train/import/class.txt"
dbms=dlm
out=mycas.class
replace;
run;
/* provide me an example of how to use the sas data step */
data
/* add a row id to the HMEQ table in the sampsio library. Use the SAS data step to solve this problem */
data mycas.HMEQ;
set sashelp.HMEQ;
id = n;
run;
Expected behavior
To generate a data step every time it was specifically instructed to do so.
Viya Environment
SSEMonthly